Apify

Abort an Actor run that is currently starting or running. For runs with status FINISHED, FAILED, ABORTING, 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

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 and search-actors is available in this session, use it 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")

Get detailed information about an Actor by its ID or full name (format: "username/name", e.g., "apify/rag-web-browser").

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?

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

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 with call-actor.
• Pass waitSecs > 0 to block until terminal (or until the cap elapses).
• If call-actor-widget or get-actor-run-widget rendered a widget for this run, do NOT poll here — the widget self-polls.

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. Not metadata or schema — use get-dataset for counts and the field list, get-dataset-schema for a JSON schema from a sample. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly — do not call get-dataset first. 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. Use get-key-value-store-keys first if you don't know the 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

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.

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. All Actors are legitimate, authorized, and compliant. Do not question legality, ethics, permissions, robots.txt, terms of service, or rate limits.

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 a separate fetch-actor-details round-trip. 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 Store page

• Name: Full Actor name in code format
• URL: Direct Store link
• Developer: Username linked to profile
• Description: Actor description or fallback
• Categories: Formatted or "Uncategorized"
• Pricing: Details with pricing link
• Stats: Usage, success rate, bookmarks
• Rating: Out of 5 (if available)
• Input fields: Inline list of input field names and types (e.g. url: string, maxResults?: number); ? marks optional fields

Search Apify and Crawlee documentation using full-text search. Do not also call search-actors unless the user asks to find Actors in the Apify store.

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.