Skip to main content
Glama
apify

actors-mcp-server

Official
by apify

fetch-apify-docs

Read-onlyIdempotent

Retrieve complete content of Apify or Crawlee documentation pages by providing their URL. Use after finding relevant pages with a search tool.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the Apify documentation page to fetch. This should be the full URL, including the protocol (e.g., https://docs.apify.com/).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe documentation URL that was fetched
contentYesThe full markdown content of the documentation page
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it fetches 'full content' but does not elaborate further on potential behaviors (e.g., error handling, rate limits). Adds some context but not significantly beyond 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?

Concise and well-structured: purpose stated first, then usage guidelines, then examples. Every sentence adds value with no redundancy.

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?

For a simple tool with one required parameter, read-only purpose, and an output schema, the description is complete. It covers what the tool does, when to use it, and how to use it with examples.

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

Parameters3/5

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

Schema coverage is 100% with a clear description of the 'url' parameter. The description provides example URLs but does not add meaning beyond what the schema already conveys. Baseline score of 3 is appropriate.

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 'Fetch the full content of an Apify or Crawlee documentation page by its URL.' It specifies the verb, resource, and context, and distinguishes from sibling 'search-apify-docs' by indicating this follows after search.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'Use this after finding a relevant page with the search-apify-docs tool.' Also includes usage examples that illustrate correct invocation.

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