Skip to main content
Glama

Get a launch video

get_video
Read-onlyIdempotent

Read a published video summary, style measurements and paginated scene cards. Video/media/music/font/logo files are never exported.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
limitNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false already in annotations, the description still adds real value: it discloses that results are paginated and that video/media/music/font/logo assets are never exported. That export-boundary statement is a behavioral fact not present in the annotations or schema.

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 short sentences, front-loaded with what is returned and followed by the important exclusion. No filler or redundancy.

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?

An output schema exists, so return-shape detail is unnecessary, and annotations cover the safety profile. The description supplies content scope, pagination and export exclusions, though it is thin on the three undocumented parameters.

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 0%, so the description must carry parameter meaning; 'paginated scene cards' loosely explains cursor/limit, and 'published video' implies what slug identifies. It never explains the slug format, limit bounds or cursor lifespan, leaving gaps a 0%-coverage schema cannot fill.

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 opens with a specific verb and resource ('Read a published video summary, style measurements and paginated scene cards'), so an agent knows the payload contents. It is not explicitly differentiated from siblings such as get_video_structure, get_scenes or get_scene, which overlap in apparent scope.

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?

Usage is only implied: 'published video' signals that unpublished content is out of scope, and 'paginated scene cards' hints at how to iterate. No sibling alternative is named and no explicit when-not condition is given.

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