Skip to main content
Glama

get_render

Read-only

Retrieves a rendered video's status, video and thumbnail URLs, file size, and staleness flag for a given render ID, so agents can check if an edited highlight needs re-rendering.

Instructions

A rendered video: status, video_url, thumbnail_url, size, and whether it is stale (highlight edited after rendering).

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": {
      "render_id": "<render_id>"
    },
    "name": "get_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
render_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value by explaining the 'stale' flag (highlight edited after rendering), which is non-obvious domain semantics. It does not say what happens for unknown ids, unrendered highlights, or whether stale renders are still served at the same URL.

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?

It is a single short sentence with no filler, which is good, but it is unstructured and front-loads the least actionable information (the return field list) rather than the usage-critical part. It reads as under-specification rather than purposeful brevity.

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

Completeness2/5

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

An output schema exists, so enumerating status, video_url, thumbnail_url and size in the description largely duplicates structured data. Meanwhile the genuinely missing pieces for a single-resource lookup tool — where render_id comes from and how it relates to the render-producing siblings — are absent.

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?

Schema description coverage is 0% for the single render_id parameter, so the description must carry the semantic load and does not: it never says where a render_id originates (a produce/render call, a job result) or its format. The entire sentence is spent on return fields instead of the one input.

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 is a noun phrase listing the fields of a render (status, video_url, thumbnail_url, size, stale) rather than a verb statement, so the retrieval action is only implied by the tool name. It does define what a 'render' is and distinguishes it conceptually from the produce-side siblings like render_highlight, but an agent gets no explicit 'retrieves a render by id' framing.

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 guidance on when to call this instead of get_job, render_highlight, or render_reel, no note that render_id comes from a render-producing call, and no mention of what to expect if the render is still pending. The agent must infer the workflow from sibling names alone.

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