Skip to main content
Glama
apify

actors-mcp-server

Official
by apify
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Search Apify docs

search-apify-docs
Read-onlyIdempotent

Search Apify platform and Crawlee documentation using full-text search. Results include page URLs and relevant content snippets.

Instructions

Search Apify and Crawlee documentation using full-text search.

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 Schema

TableJSON Schema
NameRequiredDescriptionDefault
docSourceNoDocumentation source to search. Defaults to "apify". • "apify" - Apify • "crawlee-js" - Crawlee (JavaScript) • "crawlee-py" - Crawlee (Python)apify
queryYesAlgolia 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".
limitNoMaximum 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.
offsetNoOffset 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
instructionsNoAdditional instructions for the LLM to follow when processing the search results.

Tool Definition Quality

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds context about the result format (URL + limited content) and the nature of full-text search, but does not reveal significant behavioral traits beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with bullet points for doc sources and clear instructions. Every sentence adds useful information, no redundancy. It is appropriately sized for the complexity of the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 4 parameters, an output schema, and the description explains search behavior, result format, pagination, and references the sibling tool for full content, it is fully contextualized. The additional rule about preferring platform documentation over academy content enhances completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by elaborating on doc source options and query guidelines (use keywords, not sentences). It also explains pagination with limit/offset. However, it largely repeats the schema for enum values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches Apify and Crawlee documentation with full-text search. It explicitly lists the three doc sources with detailed coverage for each, and distinguishes from sibling 'fetch-apify-docs' by advising to use that for fetching full content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit instruction to select a doc source via the parameter, and advises preferring platform documentation over academy content when both appear. It mentions using fetch-apify-docs for full content, but does not explicitly state when not to use this tool or cover all alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/apify/apify-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server