Skip to main content
Glama

Call a platform capability

call
Read-only

Call one platform-specific capability by its op ("platform.name"): what the six actions do not cover. find finds an op by what it does; capabilities lists each with its parameters and its credits per call (1 to 102). Read-only. A failed call costs 0. Ops per platform now: bilibili 1, douyin 28, google 3, instagram 1, linkedin 2, meta 5, reddit 3, tiktok 10, wechat 7, wechat_channels 8, weibo 3, x 13, xiaohongshu 21, youtube 2, zhihu 3. Pass links whole, as given. On error, follow error.fix. Tell the user billing.display. Docs: https://socialtoai.com/docs/api/call/

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": {
      "op": "<op>"
    },
    "name": "call"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesAs find and capabilities give it, like bilibili.user_posts_backup.
cursorNopage.cursor of the last answer, other arguments unchanged.
handleNoA handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run.
paramsNoThe op's own parameters, by name.
max_cost_creditsNoRefused, free, if the call would cost more.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / op / description
      Previous value: -"As find and capabilities give it, like douyin.account_audience."New value: +"As find and capabilities give it, like bilibili.user_posts_backup."
  2. Changed1 schema field changed
    • changedInput schema / properties / handle / description
      Previous value: -"A handle an earlier answer gave: reads that result, free. Nothing else is run."New value: +"A handle an earlier answer gave, or the request_id of an earlier call: reads that result again, free. Nothing else is run."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive, non-idempotent, but the description adds the pricing model (1–102 credits per op, failed call costs 0) and the recovery contract (follow error.fix, surface billing.display), which the annotations cannot convey. It does not explain how the per-platform op inventory is versioned in practice, so the disclosure is strong but not exhaustive.

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 routing sentence, then cost, then operational rules, then docs link. The 15-entry per-platform op tally is bulky but earns its place by telling the agent which platforms are actually callable; the telegraphic phrasing elsewhere occasionally costs clarity.

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 no output schema, the description still conveys the response shape indirectly through page.cursor, billing.display, and error.fix, plus the free handle re-read. Given an open-world dispatcher with nested params, the remaining gap is what a successful result body generally looks like beyond pagination.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: op must come from find/capabilities in "platform.name" form, the per-platform op counts tell the agent which namespaces exist, and 'Pass links whole, as given' constrains how URL arguments inside params must be supplied. cursor and max_cost_credits get no extra treatment beyond the schema.

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 platform-specific capability by its op') with the op format "platform.name", and explicitly positions it as the escape hatch for 'what the six actions do not cover'. An agent can tell it apart from find (lookup by behavior) and capabilities (parameter/credit inventory) without opening any schema.

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?

Names both alternatives with their distinct purposes — find locates an op by what it does, capabilities lists params and credits — and gives a when-not boundary against the fixed actions. It also sets a pre-call guardrail via max_cost_credits before spending up to 102 credits.

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.