> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Apify MCP

> AI-powered web scraping and automation platform. Run actors, scrape websites, and automate browser tasks via the official Apify MCP server.

![Apify MCP logo](https://mintcdn.com/composio-preview/6S5R4NszqpnVIZRD/images/toolkits/apify_mcp.svg?fit=max\&auto=format\&n=6S5R4NszqpnVIZRD\&q=85\&s=7e148e7d79b8089865d659576ffa88b9)

* **Category:** model context protocol
* **Auth:** DCR\_OAUTH
* **Composio-managed OAuth available?** No
* **Tools:** 12
* **Triggers:** 0
* **Slug:** `APIFY_MCP`
* **Version:** 20261018\_00

## Tools

> [accordion] Abort-actor-run
>
> **Slug:** `APIFY_MCP_ABORT_ACTOR_RUN`
>
> Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.
>
> USAGE:
>
> * Use when you need to stop a run that is taking too long or misconfigured.
>
> USAGE EXAMPLES:
>
> * user\_input: Abort run y2h7sK3Wc
> * user\_input: Gracefully abort run y2h7sK3Wc
>
> #### Input Parameters
>
> **runId** `string` *required*
>
> The ID of the Actor run to abort.
>
> **gracefully** `boolean`
>
> If true, the Actor run will abort gracefully with a 30-second timeout.
>
> #### Output
>
> **runId** `string` *required*
>
> Actor run ID
>
> **stats** `object`
>
> Run statistics
>
> **status** `string` *required*
>
> Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
>
> **actorId** `string` *required*
>
> Stable Apify Actor ID from the run record
>
> **summary** `string` *required*
>
> Past-tense summary of the run state
>
> **exitCode** `number`
>
> Actor process exit code; populated for terminal states (especially FAILED)
>
> **nextStep** `string` *required*
>
> One primary follow-up action with identifiers interpolated
>
> **storages** `object` *required*
>
> Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
>
> **actorName** `string`
>
> "username/actor-name"
>
> **startedAt** `string`
>
> ISO timestamp when the run started
>
> **finishedAt** `string`
>
> ISO timestamp when the run finished (terminal states only)
>
> **statusMessage** `string`
>
> Pass-through from Apify run.statusMessage
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the run; present only for Console sessions

> [accordion] Apify--rag-web-browser
>
> **Slug:** `APIFY_MCP_APIFY__RAG_WEB_BROWSER`
>
> This tool calls the Actor "apify/rag-web-browser" and retrieves its output results. Use this tool instead of the "call-actor" if user requests this specific Actor. Actor description: Web search and fetch tool for AI agents and RAG pipelines. It queries Google Search, scrapes the top N pages using a full web browser, and returns their content as clean Markdown for further processing by an LLM. Can also fetch individual URLs.
>
> Use this tool when user wants to GET or RETRIEVE actual data immediately (one-time data retrieval). This tool scrapes the data itself - it does NOT just find tools.
>
> Examples of when to use:
>
> * User wants current/immediate data (e.g., "Get flight prices for tomorrow", "What's the weather today?")
> * User needs to fetch specific content now (e.g., "Fetch news articles from CNN", "Get product info from Amazon")
> * User has time indicators like "today", "current", "latest", "recent", "now"
>
> This is for general web scraping and immediate data needs. For repeated/scheduled scraping of specific platforms (e-commerce, social media), consider suggesting a specialized Actor from the Store for better performance and reliability. When the user provides one specific URL and wants that page's full or verbatim content, prefer the dedicated apify/web-fetch tool when it is available - this tool is for searching and scraping by query. If a scraped page comes back blocked or empty (e.g. the crawl reports a 403 or the page text is missing), do not give up: retry that URL with the apify/web-fetch tool when it is available - its anti-bot fetching gets through blocks this tool cannot.
>
> #### Input Parameters
>
> **query** `string` *required*
>
> **REQUIRED** Enter Google Search keywords or a URL of a specific web page. The keywords might include the [advanced search operators](https://blog.apify.com/how-to-scrape-google-like-a-pro/). Examples:  - \<code>san francisco weather\</code> - \<code>[https://www.cnn.com\&lt;/code](https://www.cnn.com\&lt;/code)> - \<code>function calling site:openai.com\</code> Example values: "web browser for RAG pipelines -site:reddit.com"
>
> **waitSecs** `integer`
>
> Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
>
> **maxResults** `integer`
>
> The maximum number of top organic Google Search results whose web pages will be extracted. If `query` is a URL, then this field is ignored and the Actor only fetches the specific web page. Example values: 3
>
> **outputFormats** `array`
>
> Select one or more formats to which the target web pages will be extracted and saved in the resulting dataset. Example values: \["markdown"]
>
> #### Output
>
> **runId** `string` *required*
>
> Actor run ID
>
> **stats** `object`
>
> Run statistics
>
> **status** `string` *required*
>
> Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
>
> **actorId** `string` *required*
>
> Stable Apify Actor ID from the run record
>
> **summary** `string` *required*
>
> Past-tense summary of the run state
>
> **exitCode** `number`
>
> Actor process exit code; populated for terminal states (especially FAILED)
>
> **nextStep** `string` *required*
>
> One primary follow-up action with identifiers interpolated
>
> **storages** `object` *required*
>
> Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
>
> **actorName** `string`
>
> "username/actor-name"
>
> **startedAt** `string`
>
> ISO timestamp when the run started
>
> **finishedAt** `string`
>
> ISO timestamp when the run finished (terminal states only)
>
> **statusMessage** `string`
>
> Pass-through from Apify run.statusMessage
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the run; present only for Console sessions

> [accordion] Apify--web-fetch
>
> **Slug:** `APIFY_MCP_APIFY__WEB_FETCH`
>
> This tool calls the Actor "apify/web-fetch" and retrieves its output results. Use this tool instead of the "call-actor" if user requests this specific Actor. Actor description: Download any web page by URL and convert it to clean Markdown, plain text, HTML, and other formats. Automatically renders JavaScript and works around bot blocking. The Actor provides a real-time API for quick response times.
>
> Use this tool to fetch a specific http(s) URL and return its complete content (one URL per call; http and https only). It renders JavaScript and bypasses anti-bot protection, so it also retrieves pages where a plain HTTP fetch gets blocked, fails with an error such as 403 or 429, or returns incomplete content. The page comes back verbatim - full content, no summarization - as Markdown, plain text, HTML, the raw response body, or the list of links on the page.
>
> Examples of when to use:
>
> * User provides a URL and wants its content, its data or links, or an answer that requires reading that page
> * A previous attempt to fetch a page was blocked, returned an error or CAPTCHA, or came back incomplete because the page needs JavaScript rendering
> * Verbatim page content is needed, e.g. for quoting, extraction, or archiving
>
> This tool does not search the web - it needs a URL. To find pages by query, use a web search tool instead. If the exact URL cannot be fetched (e.g. a non-http(s) scheme), say so rather than silently substituting a different URL.
>
> #### Input Parameters
>
> **url** `string` *required*
>
> **REQUIRED** The URL to fetch. Only `http://` and `https://` schemes are supported; others are rejected. Example values: "[https://apify.com](https://apify.com)" http(s) URLs only - for any other scheme (e.g. ftp:), tell the user this tool cannot fetch it rather than substituting a different URL.
>
> **formats** `array`
>
> The Actor converts the fetched content to the requested format(s). A format that doesn't apply to the content type returns `null`; if none of the requested formats apply, the run fails. The Input form is prefilled with `markdown`; clear it to auto-select `markdown` for HTML/PDF, `text` for text-based content, or `raw` for images, archives, and other binary content. Example values: \["markdown"]
>
> **headers** `object`
>
> Custom HTTP headers to send to the target URL, as an object of header names and values, e.g. `{ "Accept-Language": "fr-FR", "Authorization": "Bearer TARGET_SITE_TOKEN" }`.
>
> **waitSecs** `integer`
>
> Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
>
> #### Output
>
> **runId** `string` *required*
>
> Actor run ID
>
> **stats** `object`
>
> Run statistics
>
> **status** `string` *required*
>
> Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
>
> **actorId** `string` *required*
>
> Stable Apify Actor ID from the run record
>
> **summary** `string` *required*
>
> Past-tense summary of the run state
>
> **exitCode** `number`
>
> Actor process exit code; populated for terminal states (especially FAILED)
>
> **nextStep** `string` *required*
>
> One primary follow-up action with identifiers interpolated
>
> **storages** `object` *required*
>
> Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
>
> **actorName** `string`
>
> "username/actor-name"
>
> **startedAt** `string`
>
> ISO timestamp when the run started
>
> **finishedAt** `string`
>
> ISO timestamp when the run finished (terminal states only)
>
> **statusMessage** `string`
>
> Pass-through from Apify run.statusMessage
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the run; present only for Console sessions

> [accordion] Call-actor
>
> **Slug:** `APIFY_MCP_CALL_ACTOR`
>
> Call any Actor from the Apify Store.
>
> WORKFLOW:
>
> 1. Use fetch-actor-details to get the Actor's input schema
> 2. Call this tool with the actor name and proper input based on the schema
>
> If the actor name is not in "username/name" format, use search-actors to resolve the correct Actor first.
>
> For MCP server Actors:
>
> * Use fetch-actor-details with output=\{ mcpTools: true } to list available tools
> * Call using format: "actorName:toolName" (e.g., "apify/actors-mcp-server:fetch-apify-docs")
>
> IMPORTANT:
>
> * Waits up to waitSecs (default 30s) for completion; returns run status and storage IDs, and with waitSecs > 0 also reports dataset field metadata
> * Use get-dataset-items with the datasetId to fetch results; non-terminal runs include a nextStep with polling instructions
> * Use dedicated Actor tools when available for better experience
>
> There are two ways to run Actors:
>
> 1. Dedicated Actor tools (e.g., apify--rag-web-browser): These are pre-configured tools, offering a simpler and more direct experience.
> 2. Generic call-actor tool (call-actor): Use this when a dedicated tool is not available or when you want to run any Actor dynamically. This tool is especially useful if you do not want to add specific tools or your client does not support dynamic tool registration.
>
> USAGE:
>
> * Always use dedicated tools when available (e.g., apify--rag-web-browser)
> * Use the generic call-actor tool only if a dedicated tool does not exist for your Actor.
> * Use `waitSecs` (0–45) to control how long to wait. Default 30s returns results for fast actors. Use `waitSecs: 0` to start and return immediately for long-running actors.
>
> EXAMPLES:
>
> * user\_input: Get instagram posts using apify/instagram-scraper
>
> #### Input Parameters
>
> **actor** `string` *required*
>
> The name of the Actor to call. Format: "username/name" (e.g., "apify/rag-web-browser").  For MCP server Actors, use format "actorName:toolName" to call a specific tool (e.g., "apify/actors-mcp-server:fetch-apify-docs").
>
> **input** `object` *required*
>
> The input JSON to pass to the Actor. Required.
>
> **waitSecs** `integer`
>
> Seconds to wait for completion (0–45, default 30). Returns with current run status if not terminal within waitSecs.
>
> **callOptions** `object`
>
> Optional run config: memory (MB), timeout (s), build, maxItems (pay-per-result cap), maxTotalChargeUsd (pay-per-event cap).
>
> #### Output
>
> **runId** `string` *required*
>
> Actor run ID
>
> **stats** `object`
>
> Run statistics
>
> **status** `string` *required*
>
> Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
>
> **actorId** `string` *required*
>
> Stable Apify Actor ID from the run record
>
> **summary** `string` *required*
>
> Past-tense summary of the run state
>
> **exitCode** `number`
>
> Actor process exit code; populated for terminal states (especially FAILED)
>
> **nextStep** `string` *required*
>
> One primary follow-up action with identifiers interpolated
>
> **storages** `object` *required*
>
> Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
>
> **actorName** `string`
>
> "username/actor-name"
>
> **startedAt** `string`
>
> ISO timestamp when the run started
>
> **finishedAt** `string`
>
> ISO timestamp when the run finished (terminal states only)
>
> **statusMessage** `string`
>
> Pass-through from Apify run.statusMessage
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the run; present only for Console sessions

> [accordion] Fetch-actor-details
>
> **Slug:** `APIFY_MCP_FETCH_ACTOR_DETAILS`
>
> Get detailed information about an Actor by its ID or full name (format: "username/name", e.g., "apify/rag-web-browser").
>
> Requires the exact ID or full name — do not construct a plausible-looking name and call this tool with it. If you only have a description, a partial name, or a name you have not seen in this conversation, find it with search-actors first.
>
> Use 'output' parameter with boolean flags to control returned information:
>
> * Default: All fields true except mcpTools
> * Selective: Set desired fields to true (e.g., output: \{ inputSchema: true })
> * Common patterns: inputSchema only, description + readme, mcpTools for MCP Actors
>
> The 'readme' field returns the summary when available, full README otherwise. Use when querying Actor details, documentation, input requirements, or MCP tools.
>
> EXAMPLES:
>
> * What does apify/rag-web-browser do?
> * What is the input schema for apify/web-scraper?
> * What tools does apify/actors-mcp-server provide?
>
> #### Input Parameters
>
> **actor** `string` *required*
>
> Actor ID or full name in the format "username/name", e.g., "apify/rag-web-browser".
>
> **output** `object`
>
> Specify which information to include in the response to save tokens.
>
> #### Output
>
> **readme** `string`
>
> Actor README summary when available, otherwise the full README documentation.
>
> **mcpTools** `string`
>
> Markdown listing of MCP tools exposed by the Actor (only present when `output.mcpTools` is requested).
>
> **actorInfo** `object`
>
> **inputSchema** `object`
>
> Actor input schema.
>
> **outputSchema** `object`
>
> Output schema inferred from successful runs.

> [accordion] Fetch-apify-docs
>
> **Slug:** `APIFY_MCP_FETCH_APIFY_DOCS`
>
> Fetch the full content of an Apify or Crawlee documentation page by its URL. Use this after finding a relevant page with the search-apify-docs tool.
>
> USAGE:
>
> * Use when you need the complete content of a specific docs page for detailed answers.
>
> USAGE EXAMPLES:
>
> * user\_input: Fetch [https://docs.apify.com/platform/actors/running#builds](https://docs.apify.com/platform/actors/running#builds)
> * user\_input: Fetch [https://docs.apify.com/academy](https://docs.apify.com/academy)
> * user\_input: Fetch [https://crawlee.dev/docs/guides/basic-concepts](https://crawlee.dev/docs/guides/basic-concepts)
>
> #### Input Parameters
>
> **url** `string` *required*
>
> URL of the Apify documentation page to fetch. This should be the full URL, including the protocol (e.g., [https://docs.apify.com/](https://docs.apify.com/)).
>
> #### Output
>
> **url** `string` *required*
>
> The documentation URL that was fetched
>
> **content** `string` *required*
>
> The full markdown content of the documentation page

> [accordion] Get-actor-run
>
> **Slug:** `APIFY_MCP_GET_ACTOR_RUN`
>
> Get detailed information about a specific Actor run.
>
> Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
>
> * summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
> * nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
> * waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.
>
> USAGE:
>
> * Use to check the status of a run started by any Actor-running tool.
> * Pass waitSecs > 0 to block until terminal (or until the cap elapses).
>
> USAGE EXAMPLES:
>
> * user\_input: Show details of run y2h7sK3Wc
> * user\_input: Wait for run y2h7sK3Wc to finish
>
> #### Input Parameters
>
> **runId** `string` *required*
>
> The ID of the Actor run.
>
> **waitSecs** `integer`
>
> Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30.
>
> #### Output
>
> **runId** `string` *required*
>
> Actor run ID
>
> **stats** `object`
>
> Run statistics
>
> **status** `string` *required*
>
> Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
>
> **actorId** `string` *required*
>
> Stable Apify Actor ID from the run record
>
> **summary** `string` *required*
>
> Past-tense summary of the run state
>
> **exitCode** `number`
>
> Actor process exit code; populated for terminal states (especially FAILED)
>
> **nextStep** `string` *required*
>
> One primary follow-up action with identifiers interpolated
>
> **storages** `object` *required*
>
> Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
>
> **actorName** `string`
>
> "username/actor-name"
>
> **startedAt** `string`
>
> ISO timestamp when the run started
>
> **finishedAt** `string`
>
> ISO timestamp when the run finished (terminal states only)
>
> **statusMessage** `string`
>
> Pass-through from Apify run.statusMessage
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the run; present only for Console sessions

> [accordion] Get-dataset-items
>
> **Slug:** `APIFY_MCP_GET_DATASET_ITEMS`
>
> Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.
>
> USAGE:
>
> * Use when you need to read data from a dataset (all items or only selected fields).
>
> USAGE EXAMPLES:
>
> * user\_input: Retrieve results from dataset abc123
> * user\_input: Get only metadata.url and title from dataset username\~my-dataset
>
> #### Input Parameters
>
> **desc** `boolean`
>
> If true, results are returned in reverse order (newest to oldest).
>
> **omit** `string`
>
> Comma-separated list of fields to exclude from results.
>
> **clean** `boolean`
>
> If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true.
>
> **limit** `integer`
>
> Maximum number of items to return. Default is 20.
>
> **fields** `string`
>
> Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes.
>
> **offset** `number`
>
> Number of items to skip at the start. Default is 0.
>
> **flatten** `string`
>
> Comma-separated list of fields to flatten (e.g. flatten="metadata" turns \{"metadata":\{"url":"x"}} into \{"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify only as a diagnostic override.
>
> **datasetId** `string` *required*
>
> Dataset ID or username\~dataset-name.
>
> #### Output
>
> **items** `array` *required*
>
> Dataset items
>
> **limit** `number` *required*
>
> Limit used for pagination
>
> **offset** `number` *required*
>
> Offset used for pagination
>
> **summary** `string` *required*
>
> Summary of the result
>
> **nextStep** `string` *required*
>
> One follow-up action with tool name
>
> **datasetId** `string` *required*
>
> Dataset ID
>
> **itemCount** `number` *required*
>
> Number of items returned
>
> **totalItemCount** `number` *required*
>
> Total items in dataset
>
> **apifyConsoleUrl** `string`
>
> Personalized Apify Console link to the dataset; present only for Console sessions

> [accordion] Get-key-value-store-record
>
> **Slug:** `APIFY_MCP_GET_KEY_VALUE_STORE_RECORD`
>
> Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.
>
> USAGE:
>
> * Use when you need to retrieve a specific record (JSON, text, or binary) from a store.
>
> USAGE EXAMPLES:
>
> * user\_input: Get record INPUT from store abc123
> * user\_input: Get record data.json from store username\~my-store
>
> #### Input Parameters
>
> **recordKey** `string` *required*
>
> Key of the record to retrieve.
>
> **keyValueStoreId** `string` *required*
>
> Key-value store ID or username\~store-name.
>
> #### Output
>
> **key** `string` *required*
>
> Record key
>
> **value** `string` *required*
>
> The stored value (JSON, text, or binary)
>
> **summary** `string` *required*
>
> Summary of the result
>
> **contentType** `string`
>
> MIME type of the stored value
>
> **keyValueStoreId** `string` *required*
>
> Key-value store ID

> [accordion] Report-problem
>
> **Slug:** `APIFY_MCP_REPORT_PROBLEM`
>
> Report a problem with Apify's MCP tools or Actors to the Apify team.
>
> Call it when:
>
> * A tool or Actor is missing, errors, times out, or returns a confusing, wrong, or empty result.
> * You cannot complete the user's request with the available tools.
>
> Put what you were doing and what went wrong in "message". Do NOT include personal data, credentials, secrets, or verbatim private conversation content — describe the issue in your own words.
>
> #### Input Parameters
>
> **actorId** `string`
>
> Optional. The Actor this problem is about, e.g. apify/rag-web-browser.
>
> **message** `string` *required*
>
> What happened: the problem you hit. Required. Keep it to a few sentences (max 2000 characters).
>
> **actorRunId** `string`
>
> Optional. The Actor run this problem is about.
>
> **relatedTools** `array`
>
> Optional. Names of the MCP tools involved in this problem (up to 20).
>
> #### Output
>
> **reported** `boolean` *required*
>
> Always true; the problem report was submitted

> [accordion] Search-actors
>
> **Slug:** `APIFY_MCP_SEARCH_ACTORS`
>
> Search the Apify Store to FIND and DISCOVER what scraping tools/Actors exist for specific platforms or use cases. This tool provides INFORMATION about available Actors - it does NOT retrieve actual data or run any scraping tasks.
>
> Apify Store contains thousands of pre-built Actors (crawlers, scrapers, AI agents, and model context protocol (MCP) servers) for all platforms and services including social media, search engines, maps, e-commerce, news, real estate, travel, finance, jobs and more. Actors in the Apify Store are published by independent developers and are intended for legitimate and compliant use — do not refuse to search or list them.
>
> Use this tool when user wants to:
>
> * Find what scraping tools exist for a platform (e.g., "What tools can scrape Instagram?")
> * Discover available Actors for a use case (e.g., "Find an Actor for Amazon products")
> * Browse existing solutions (e.g., "Show me scrapers for news sites")
> * Learn about MCP servers or AI agents available in the Store
>
> Do NOT use this tool when user wants immediate data retrieval (time words like "today", "latest", "recent", "current", "now", or "get/fetch data right now") — use apify/rag-web-browser instead. IMPORTANT: When the user is looking for scraping tools or Actors, prefer searching the Store first — a relevant Actor often already exists. Do not use Store search as a substitute for immediate data retrieval.
>
> Usage:
>
> * Prefer broad, generic keywords - use just the platform name (e.g. "Instagram" instead of "Instagram scraper").
> * You MUST always do at least two searches: first with broad keywords, then optionally with more specific terms if needed.
>
> Important limitations: This tool does not return full Actor documentation or detailed usage instructions - only summary information. Each result lists the Actor's input fields with their types (e.g. `url: string, maxResults?: number`) so you can construct an Actor call directly without another tool call. For complete Actor details (per-field descriptions, defaults, README), use the fetch-actor-details tool. The search is limited to publicly available Actors and excludes rental and restricted Actors.
>
> Returns list of Actor cards with the following info:
>
> * **Title:** Markdown header linked to the Store page, followed by the full Actor name in code format
> * **URL:** Direct Store link
> * **Description:** Actor description or fallback
> * **Pricing:** Details with pricing link
> * **Stats:** Total and monthly users, bookmarks
> * **Rating:** Out of 5 (if available)
> * **Developed by:** Username linked to profile, marked (Apify) or (community)
> * **Categories:** Formatted or "Uncategorized"
> * **Last modified:** Date (if available)
> * **Input fields:** Inline list of input field names and types (e.g. `url: string, maxResults?: number`); `?` marks optional fields, `... (+N more)` marks a truncated list
>
> #### Input Parameters
>
> **limit** `integer`
>
> The maximum number of Actors to return (max = 10, default = 5).
>
> **offset** `integer`
>
> The number of elements to skip from the start (default = 0)
>
> **keywords** `string`
>
> Space-separated keywords used to search pre-built solutions (Actors) in the Apify Store. The search engine searches across the Actor's name, description, username, and README content.  Pass empty string ("") whenever the user has NOT named a specific platform (Instagram, Amazon, Google Maps) or a specific data type (posts, products, weather, news). Empty keywords return Actors in the Apify Store's default sort order, which is popularity in practice (most-used Actors first). Do NOT use ranking words ("top", "best", "popular") or bare task words ("scraper", "crawler", "extractor") as keyword values — they are not Actor names and produce noisy matches against README content.  Otherwise, follow these rules: - Use 1-3 simple keyword terms maximum (e.g., "Instagram posts", "Twitter", "Amazon products") - Actors are named using platform or service name together with the type of data or task they perform - The most effective keywords are specific platform names (Instagram, Twitter, TikTok) and specific data types (posts, products, profiles, weather, news, reviews, comments) - If a user asks about "fetching Instagram posts", use "Instagram posts" as keywords - The goal is to find Actors that specifically handle the platform and data type the user mentioned  Examples: ✅ "Instagram posts", "Twitter", "Amazon products", "TikTok comments" ✅ "" (empty) — returns the most popular Actors store-wide ❌ "Instagram posts profiles comments hashtags reels stories followers..." (too long) ❌ "top popular actors", "best scrapers", "trending" — ranking words aren't Actor keywords; pass "" instead ❌ "scraper", "extractor", "web crawler" — bare task words aren't Actor keywords; pass "" instead
>
> #### Output
>
> **count** `number` *required*
>
> Number of Actors returned
>
> **query** `string` *required*
>
> The search query used
>
> **actors** `array` *required*
>
> List of Actor cards matching the search query
>
> **userTier** `string ("FREE" | "BRONZE" | "SILVER" | "GOLD" | "PLATINUM" | "DIAMOND")`
>
> The user's plan tier used to resolve the per-Actor pricing shown in the results
>
> **instructions** `string`
>
> Additional instructions for the LLM to follow when processing the search results.

> [accordion] Search-apify-docs
>
> **Slug:** `APIFY_MCP_SEARCH_APIFY_DOCS`
>
> Search Apify and Crawlee documentation using full-text search. Do not also search the Apify Store unless the user asks to find Actors.
>
> You must explicitly select which documentation source to search using the docSource parameter:
>
> • docSource="apify" - Apify: Apify Platform documentation including: Platform features, SDKs (JS, Python), CLI, REST API, Academy (web scraping fundamentals), Actor development and deployment
>
> • docSource="crawlee-js" - Crawlee (JavaScript): Crawlee is a web scraping library for JavaScript. It handles blocking, crawling, proxies, and browsers for you.
>
> • docSource="crawlee-py" - Crawlee (Python): Crawlee is a web scraping library for Python. It handles blocking, crawling, proxies, and browsers for you.
>
> The results will include the URL of the documentation page (which may include an anchor), and a limited piece of content that matches the search query.
>
> Fetch the full content of the document using the fetch-apify-docs tool by providing the URL.
>
> When results contain both platform documentation (`docs.apify.com/platform`) and Academy content (`docs.apify.com/academy`) on the same topic, prefer the platform documentation.
>
> #### Input Parameters
>
> **limit** `number`
>
> Maximum number of search results to return. Defaults to 5. Maximum is 20. You can increase this limit if you need more results, but keep in mind that the search results are limited to the most relevant pages.
>
> **query** `string` *required*
>
> Algolia full-text search query to find relevant documentation pages. Use only keywords, do not use full sentences or questions. For example, "standby actor" will return documentation pages that contain the words "standby" and "actor".
>
> **offset** `number`
>
> Offset for the search results. Defaults to 0. Use this to paginate through the search results. For example, if you want to get the next 5 results, set the offset to 5 and limit to 5.
>
> **docSource** `string ("apify" | "crawlee-js" | "crawlee-py")`
>
> Documentation source to search. Defaults to "apify". • "apify" - Apify • "crawlee-js" - Crawlee (JavaScript) • "crawlee-py" - Crawlee (Python)
>
> #### Output
>
> **results** `array` *required*
>
> **instructions** `string`
>
> Additional instructions for the LLM to follow when processing the search results.
