Skip to main content
Glama

Search launch scenes

search_scenes
Read-onlyIdempotent

Main scene search. Finds launch-video scenes from a plain description ("a cursor clicks Export and the file appears") and/or taxonomy filters. Each of the first 12 results comes with a signed image you can see (key frame and its progression), plus image_url and launchscene_url. Each result also carries its film (title, duration, scene count, order of passages) and the scene's position in it, so open get_video only for the full scene list. Only published references, each with its annotation_status; filters apply to each scene and unknown measurements are excluded. Scenes of clips are included (film.kind is "clip": a short loop or site footage that is a scene reference, not a launch film); filters.kind narrows to "film" or "clip".

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_scenes"
  }
}

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.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that only the first 12 results carry signed images, that each result embeds film metadata and scene position, that only published references are returned with annotation_status, and that filters apply per scene with unknown measurements excluded. It also pre-empts a confusing case by explaining that clip scenes appear and how film.kind distinguishes them.

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?

Front-loaded with the one-line purpose, then progressively detailed. Dense but mostly earning its space; the nested parentheticals ("(film.kind is \"clip\": a short loop...)") make it slightly run-on for a single paragraph.

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, nested-filter search tool that already has an output schema, the description covers result contents, filtering behavior and edge cases (unpublished excluded, unknown measurements dropped, clips included). Remaining gaps are the sort/limit/cursor semantics that determine pagination behavior.

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%, and the description compensates for query, filters.kind and images (signed image for the first 12) but says nothing about sort, limit or cursor semantics. Coverage is partial, so the baseline-not-exceeded score of 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Main scene search. Finds launch-video scenes") plus the two input modes (plain description and/or taxonomy filters). It also explicitly distinguishes itself from get_video ("open get_video only for the full scene list"), so an agent can route between them without opening schemas.

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?

Gives clear context for what this tool returns and names get_video as the alternative when the full scene list is needed, plus guidance on filters.kind narrowing to film or clip. It does not address other plausible alternatives such as search_by_moment, pattern_search or search_videos directly in the description text.

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