Skip to main content
Glama

Build an MCP client config

build_mcp_config
Read-onlyIdempotent

Ready-to-paste config that adds chosen Actors (or a website's bundle) to an MCP client through Apify's hosted MCP server: Claude Code, Claude Desktop, Cursor, VS Code, ChatGPT, Codex CLI, Gemini CLI or n8n AI Agent, with steps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_mcp_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorsNoActor ids (owner/name) to include.
clientNoall
websiteNoOr: a website whose main Actors to bundle, e.g. 'TikTok'.
server_nameNoOptional server name in the config.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, disclosing that the result is a paste-ready config plus 'steps' delivered through Apify's hosted MCP server. It does not say whether the tool stores anything or what happens if both actors and website are supplied.

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?

One front-loaded sentence that leads with the deliverable ('Ready-to-paste config') before the client enumeration. The long client list is dense but serves a real purpose by signaling supported targets; nothing is redundant.

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?

With four optional parameters, no output schema, and annotations covering the safety profile, the description is nearly sufficient — it conveys both the config artifact and accompanying steps. The remaining gap is precedence when actors and website are both provided, which neither schema nor description resolves.

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 75%, so the schema already documents actors, client, and website, including the enum and the 'Or:' framing for website. The description adds only the actors/website either-or framing in prose and omits server_name entirely, so it does little beyond the structured fields.

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

Purpose4/5

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

States a concrete deliverable: a 'Ready-to-paste config' that adds chosen Actors (or a website's bundle) to an MCP client via Apify's hosted MCP server. The purpose is unmistakable and clearly distinct from siblings like get_tool or troubleshoot, though it never names those siblings to route against.

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

Usage Guidelines3/5

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

Usage is implied by the output type: use this when you need setup instructions for wiring Actors into an MCP client. There is no explicit when-not guidance, no stated prerequisites, and no named alternative for adjacent needs (e.g., searching for Actors first, or troubleshooting an existing setup).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources