Skip to main content
Glama
apify

actors-mcp-server

Official
by apify
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Fetch Actor details

fetch-actor-details
Read-onlyIdempotent

Retrieve comprehensive details about any Apify Actor including its description, input schema, README, pricing, stats, and MCP tools. Specify exactly which information to fetch to optimize token usage.

Instructions

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?

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actorYesActor ID or full name in the format "username/name", e.g., "apify/rag-web-browser".
outputNoSpecify which information to include in the response to save tokens.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
readmeNoActor README summary when available, otherwise the full README documentation.
mcpToolsNoMarkdown listing of MCP tools exposed by the Actor (only present when `output.mcpTools` is requested).
actorInfoNo
inputSchemaNoActor input schema.
outputSchemaNoOutput schema inferred from successful runs.

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent. Description adds behavior details like how 'readme' returns summary vs full README, and that 'outputSchema' is inferred from recent runs.

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

Conciseness4/5

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

Well-structured with clear sections and front-loaded purpose, though could be slightly more concise.

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?

Comprehensive for a tool with nested parameters; covers output control, examples, and context. Output schema exists, so description need not explain return structure.

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

Parameters5/5

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

Adds significant value beyond the schema: explains actor format, default output, selective patterns, and common use cases. Schema coverage is 100% but description enriches understanding.

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 retrieves detailed information about an Actor by ID or full name, distinguishing it from sibling tools like search-actors and call-actor.

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 use cases (querying Actor details, documentation, input requirements, MCP tools) and examples, though it could be more explicit about when not to use compared to 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