Skip to main content
Glama
actors-mcp-server

actors-mcp-server

Official
by apify

Fetch Actor MCP tool list

fetch-actor-mcp-tool-list

Lists an Actor's available MCP tools with names, descriptions, input schemas, annotations, and metadata, so you can check which tools it provides before calling one by name.

Instructions

List an Actor's MCP tools with each tool's name, description, input schema, annotations, and metadata, as the server reports them. call-actor-mcp-tool calls one of them by name. Each call asks the server again; nothing is cached. 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.

USAGE:

  • Use when the user asks which MCP tools an Actor provides, or before calling one of them.

USAGE EXAMPLES:

  • user_input: What tools does username/name provide?

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>"
    },
    "name": "fetch-actor-mcp-tool-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesThe MCP server Actor: its ID, or its name in the "username/name" form.

Output Schema

NameRequiredDescriptionDefault
toolsYesThe tools on the Actor's MCP server, with their schemas, annotations and metadata.

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.4/5.0
Behavior5/5

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

With readOnlyHint=false and idempotentHint=false already set, the description supplies the reasoning an agent needs: nothing is cached and each call re-queries the server, it authenticates with the caller's Apify API token, connecting may launch a Server Actor run that persists until idle timeout, and multi-tenant servers bill per event. Those side-effect and cost disclosures go well beyond what the annotations convey.

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?

The first sentence front-loads the action and return contents, and the following sentences each carry a distinct fact about caching, auth, run lifetime, and billing. The usage example is mildly redundant with the usage line but not wasteful.

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?

An output schema exists, so return values need no elaboration, and the annotations are complemented by the description's billing and run-lifecycle notes. For a one-parameter listing tool that spawns a server run, nothing an agent needs to call it safely is missing.

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?

The single parameter is fully documented in the schema, including the accepted ID and "username/name" forms, so the schema already carries the semantics. The description adds no further syntax or format detail about the actor argument, making 3 the correct baseline.

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 gives a specific verb and resource ("List an Actor's MCP tools") and enumerates the returned fields (name, description, input schema, annotations, metadata). It also explicitly distinguishes itself from the sibling that invokes those tools, noting "call-actor-mcp-tool calls one of them by name."

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?

It states a clear trigger ("Use when the user asks which MCP tools an Actor provides") and a proactive trigger ("or before calling one of them"), and pairs that with the alternative invocation tool. It does not spell out exclusions or failure conditions, which keeps it just short of a 5.

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