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. Apify Store lists Actors published by Apify and by independent developers.

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

This tool discovers Actors; it does not retrieve their output. IMPORTANT: When the user wants detailed data from a specific platform or is looking for scraping tools, prefer searching the Store first — a relevant Actor often already exists. When the user names a specific Actor, look up that Actor directly instead of searching.

Usage:

• Use 1-3 simple terms from the platform and/or data type the user named (e.g. "Instagram posts", "Twitter", "Amazon products"). With neither named, empty keywords return the Store's default ordering. A platform-only query is an option if more specific results do not fit.

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

• 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

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' to control returned information:

• Default: all fields except outputSchema and serverInterface.

• Selective: set only the fields you need to true, e.g. output: { inputSchema: true }

• Common patterns: inputSchema only, description + readme, serverInterface: true (every operation in full when they fit, one line per operation otherwise) or "GET /search" (one operation in full) for Server Actors

The 'readme' field returns the summary when available, full README otherwise. Use when querying Actor details, documentation, or input requirements. It does not connect to an MCP server Actor; fetch-actor-mcp-tool-list lists its MCP tools.

EXAMPLES:

• What does apify/web-fetch do?

• What is the input schema for apify/web-scraper?

• What HTTP operations does this Server Actor expose?

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.

MCP server Actors are not run here; call-actor-mcp-tool calls their MCP tools.

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: 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

• 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

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

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

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

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

List an Actor's MCP tools with each tool's name, description, input schema, annotations, and metadata, as the server reports them. call-actor-mcp-tool calls one of them by name. Each call asks the server again; nothing is cached. It connects with your Apify API token. Connecting can start a Server Actor run in your account, kept until its idle timeout; a multi-tenant Server Actor charges per event.

USAGE:

• Use when the user asks which MCP tools an Actor provides, or before calling one of them.

USAGE EXAMPLES:

• user_input: What tools does username/name provide?

Call one tool on an Actor's MCP server and return its result. fetch-actor-mcp-tool-list lists the Actor's MCP tools and their input schemas. It connects with your Apify API token. Connecting can start a Server Actor run in your account, kept until its idle timeout; a multi-tenant Server Actor charges per event. What the tool itself does depends on the Actor.

Example call: {"actor": "username/name", "tool": "search", "arguments": {"query": "apify"}}

USAGE:

• Use when the user asks to call a tool on an Actor's MCP server.

USAGE EXAMPLES:

• user_input: Use the search tool of username/name to look up apify

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.

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

• user_input: Fetch https://docs.apify.com/academy

• user_input: Fetch https://crawlee.dev/docs/guides/basic-concepts

Report a problem with Apify's MCP tools or Actors to the Apify team.

Reports can describe missing tools or Actors, errors, timeouts, confusing results, steps that took several attempts, or tasks that the available tools could not complete. Reports help fix the problem for other users.

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.