Skip to main content
Glama

Get an upload or link

get_upload
Read-onlyIdempotent

A video added with commit_upload or add_video_link: status probing → ready (duration_s known) | failed.

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": {
      "source_id": "<source_id>"
    },
    "name": "get_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare a safe, idempotent read operation. The description adds useful lifecycle context: probing leads to ready with duration_s known, or failed. It does not explain polling expectations, error behavior, or what the response contains beyond the status implications.

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

Conciseness3/5

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

The description is very short and front-loads the relevant lifecycle information, but the arrow notation and sentence fragment make it cryptic. It avoids waste but sacrifices clarity for brevity.

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 simple read-only status tool, the description conveys the meaningful status outcomes and the source of the video. It still omits the meaning of the required source_id and does not clearly state that the caller should poll or what is returned, leaving an important gap given there is no output schema.

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

Parameters2/5

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

There is one required source_id parameter with 0% schema description coverage, and the description never explains what source_id represents or where it comes from. It only loosely ties the tool to videos added by commit_upload or add_video_link, which is insufficient for a required identifier parameter.

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

Purpose3/5

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

The description identifies the resource as a video added via commit_upload or add_video_link and implies a status check, but it uses a fragment rather than stating a clear verb such as retrieve or check. It does not explicitly say the tool returns the upload/link state, leaving the core action somewhat inferred.

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?

The mention of commit_upload and add_video_link implies this tool is used after those calls to probe status, and the lifecycle states suggest polling until ready or failed. However, it does not explicitly state when to use this instead of get_video or other retrieval tools.

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.