Skip to main content
Glama

Social0

get_publish_status

Read-onlyIdempotent

Check the publishing status of a post using its tracking ID. Returns overall status, per-platform progress, and any errors.

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": {
      "tracking_id": "<tracking_id>"
    },
    "name": "get_publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracking_idYesTracking ID returned from publish operations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuine value by disclosing the return shape (overall status, per-platform progress, errors), which matters because there is no output schema. It stops short of stating whether status is terminal or how often to poll, which would complete the picture.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and followed by the return payload. No filler or redundant restatement of the tool name.

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 a one-parameter read tool with no output schema, the description supplies the essentials: what it looks up, the key it needs, and what comes back. The only gap is operational context around polling/status finality, a minor omission given the annotations already cover the safety profile.

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 description coverage is 100% and the single tracking_id parameter is fully documented as a UUID from publish operations. The description's phrase 'using its tracking ID' restates the schema rather than adding new semantics, so baseline 3 is appropriate.

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?

The description pairs the specific verb 'Check' with the resource 'publishing status of a post' and adds the lookup key ('tracking ID'). It is distinguishable from siblings like get_post or get_analytics by focusing on publish progress, though it never names an alternative to make the distinction explicit.

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 only implied: the reference to 'tracking ID returned from publish operations' suggests calling this after publish_now/publish_post/schedule_post, and the schema reinforces that. There is no explicit when-to-use vs. when-not guidance or named alternative for retrieving post details instead.

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.