Skip to main content
Glama
actors-mcp-server

actors-mcp-server

Official
by apify

Call Actor MCP tool

call-actor-mcp-tool
Destructive

Call a specific tool on an Actor's MCP server and return its result. Use it to run Actor capabilities like search with your schema-defined arguments.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actor": "<actor>",
      "tool": "<tool>"
    },
    "name": "call-actor-mcp-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe name of the tool on the Actor's MCP server.
actorYesThe MCP server Actor: its ID, or its name in the "username/name" form.
argumentsNoThe tool's arguments, matching its input schema. Omit for a tool that takes none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.21.10
    • addedInput schema / properties / actor / maxLength
      Added value: +256
  2. Addedv0.19.5

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that it authenticates with the user's Apify API token, may start a Server Actor run in their account that persists until an idle timeout, and that a multi-tenant Server Actor charges per event. It also warns that actual side effects depend on the target Actor, which matters given destructiveHint=true and openWorldHint=true.

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?

Front-loaded with the core action, then scope, cost/credential caveats, and an example — each sentence carries information. The separate USAGE and USAGE EXAMPLES headings add some structural overhead for a description of this length, but no sentence is filler.

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

Completeness4/5

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

For an open-world, non-idempotent proxy tool with no output schema, the description covers credentials, cost, run lifecycle, and the fact that return shape is Actor-dependent. It could say more about what errors or result structure to expect, but the essential operational context is present.

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%, so the schema already documents actor, tool, and arguments. The worked example call adds a concrete illustration of how the three parameters combine, but no additional semantics about actor ID formats or argument validation beyond what the schema states.

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?

States a specific verb and resource: call one tool on an Actor's MCP server and return its result. It also explicitly distinguishes itself from fetch-actor-mcp-tool-list, which lists the tools and input schemas rather than invoking them, so an agent can route correctly without opening either schema.

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?

Gives a clear trigger ("Use when the user asks to call a tool on an Actor's MCP server") and a concrete usage example mapping user intent to actor/tool/arguments. The implicit prerequisite of discovering tool names via fetch-actor-mcp-tool-list is stated as a fact rather than as a required step, and no explicit when-not guidance is given.

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