Skip to main content
Glama

How an upload is going

publish_status

Check a clip's upload progress, or view recent uploads when no clip is specified.

Instructions

Where a clip's upload has got to, or the recent uploads when no clip is named.

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": "publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. 'Has got to' implies a read, but read-only-ness is never stated, and the fallback mode is left undefined on the points that matter: how many recent uploads, over what window, and whether results are paginated or truncated.

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 sentence, front-loaded with the primary behavior and ending on the no-argument case, with no filler. The colloquial phrasing 'has got to' costs a little precision but the sentence earns its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional parameter with no annotations and no output schema, the description should say more about what comes back — field names, upload states, or the size of the recent-uploads list — since nothing else documents the return shape. It covers the two calling modes adequately but leaves the result undefined.

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 0%, so the description must supply the meaning of clip_id, and it does: the parameter scopes the lookup to a single clip, and its absence switches the tool to a listing mode. That conditional behavior is genuinely beyond the bare schema. It stops short of saying where the ID comes from or that it is an integer identifier.

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 names a specific resource: the progress of a clip's upload, plus a fallback mode that returns recent uploads. It is clear enough to know what the tool reports, but it never distinguishes itself from the crowded status family (job_status, queue_status, uploadpost_status, youtube_status), so an agent cannot tell which status tool answers which question.

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?

There is conditional guidance implicit in 'or the recent uploads when no clip is named' — supply clip_id for one clip, omit it to browse. That is genuine usage signal. However, there is no guidance on when to pick this over the many sibling status tools, and no prerequisites or exclusions.

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