Skip to main content
Glama

Where a clip ended up

uploadpost_result

Retrieve per-platform publishing status and links for a clip sent through Upload-Post, showing which platforms succeeded or failed and why.

Instructions

Per-platform state and links for a clip published through Upload-Post: which platforms went out, which failed and why.

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": {
      "clip_id": "<clip_id>"
    },
    "name": "uploadpost_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does useful work by describing the return content (per-platform state, links, failure reasons), which partly substitutes for the missing output schema, but it never states that this is a read-only lookup, what happens if the clip has not been published yet or is still in flight, or how errors surface.

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?

A single compact sentence with no filler, front-loaded on the core result (per-platform state and links) before the outcome breakdown. Nothing is wasted, though the brevity is partly the source of the definition's gaps.

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 lookup with no output schema or annotations, the description conveys enough about the return payload (which platforms went out, which failed and why, plus links) for the agent to know what it is asking for. It remains thin on failure modes and on the clip_id input, which keeps it out of the top score.

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?

With a single parameter at 0% schema description coverage, the description must supply the meaning of clip_id, and it does not — it never names the identifier or says where to obtain it. The schema only types it as an integer, so the description leaves the one input under-specified.

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 title and description together state a specific resource: per-platform publication state and links for a clip published through Upload-Post, including which platforms succeeded and which failed. The verb is only implied ('result'), and it does not distinguish itself from the sibling uploadpost_status, so an agent cannot tell from the text alone which of the two to reach for.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of the related uploadpost_publish or uploadpost_status tools, and no stated precondition (e.g. that the clip must already be published). The agent must infer usage from the name and from the sibling names alone.

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