Skip to main content
Glama

Search launch videos

search_videos
Read-onlyIdempotent

Main search for whole launch films. Finds published launch videos by description, brand, industry, timing, sound or style. Each of the first 12 results comes with a signed image of its scenes, colored by narrative role. Score is relevance, not quality. Clips (short loops and site footage that announce nothing by themselves) are left out unless filters.kind is "clip" or "any".

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

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
limitNo
queryNo
cursorNo
imagesNoReturn a signed image for each of the first 12 results (true by default)
filtersNo

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / filters / properties / kind
      Added value: +{
      +  "description": "film: launch films only. clip: short loops and site footage that announce nothing by themselves. any: both. search_videos defaults to film, search_scenes to any.",
      +  "enum": [
      +    "film",
      +    "clip",
      +    "any"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover safety (read-only, idempotent, closed-world), and the description adds real behavioral detail beyond them: the first 12 results carry a signed image of their scenes colored by narrative role, and the score is relevance rather than quality. It also discloses the default exclusion of clips, which is non-obvious behavior an agent would otherwise only discover from the schema.

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?

Four tight sentences, front-loaded with the primary purpose and ending with the exclusion rule. The parenthetical defining clips largely restates the schema's kind enum description, costing a little efficiency but aiding standalone readability.

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 6-parameter tool with an 18-property nested filters object and an output schema, the description covers the decisions an agent most needs: what corpus is searched, what comes back with images, and default clip exclusion. Pagination via cursor and differing sort orders are left entirely to the schema, which is a minor gap given the output schema already handles return values.

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 only 17%, so the description must carry weight; it explains the images behavior, the effective default of filters.kind=film, and what relevance scoring means. However, most filters (tone, aspect, bpm, pace, background, duration, dates) and the sort options go undiscussed, so compensation is only partial.

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 gives a specific verb and resource - searching published launch films - and states the matchable dimensions (description, brand, industry, timing, sound, style). It also draws a clear boundary by excluding clips. It does not name the sibling (search_scenes) that the schema's kind description points to, so sibling routing lives in structured data rather than the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Main search for whole launch films" signals this is the default entry point, and the last sentence gives an explicit rule for when clips appear (only via filters.kind "clip" or "any"). What is missing is a direct pointer to the alternative tool for scene-level or moment-level lookups.

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