Skip to main content
Glama

Get video

get_video
Read-onlyIdempotent

Read one video file by media ID. Returns its stable link, source, brand, MIME type, size, duration, description, and Library status.

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": {
      "id": "<id>"
    },
    "name": "get_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMedia ID of the video file, from list_videos or a generation output's id.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
idYesMedia ID of the file.
urlYesStable link to the file.
typeYesMedia family: image, video, or audio.
widthYesWidth in pixels, or null when not recorded.
heightYesHeight in pixels, or null when not recorded.
sourceYesuploaded, scraped (collected from a brand source), or generated.
file_sizeYesFile size in bytes.
mime_typeYesMIME type of the file.
created_atYesTime the file was stored.
in_libraryYesWhether the file is in its Brand Library.
descriptionYesText description of the file, or null when there is none.
duration_msYesDuration in milliseconds, or null when not recorded.
workspace_idYesWorkspace ID, or null for a personal workspace that has no ID.
generation_idYesID of the generation that produced the file, or null when none is recorded.
brand_session_idYesBrand session ID of the brand the file belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the enumeration of returned attributes, but says nothing about not-found behavior, permissions, or whether the link expires — which is the kind of context that would earn a higher score.

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 tight sentences with the operation and its output front-loaded and zero filler. Nothing in the text is redundant with itself or padded.

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 simple, read-only, idempotent single-record fetch with a fully described schema and an output schema, the description covers purpose and return shape adequately. The remaining gap is edge-case behavior on a missing or inaccessible ID, which is minor for this tool class.

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%, so both parameters (id and the optional llm_model analytics field) are already documented in the schema, including the note that llm_model can be omitted. The description adds no syntax, format, or meaning beyond that, making the baseline of 3 correct.

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?

States a specific verb and resource — 'Read one video file by media ID' — which distinguishes a single-item fetch from a listing operation. It does not name a sibling alternative explicitly, so it falls just short of the top mark.

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?

The description offers no when-to-use guidance, no statement of when not to use it, and no reference to alternatives such as list_videos or generate_video. The only clue that it is for retrieving an existing item is the phrase 'by media ID', which is implied rather than stated.

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.

Resources