Skip to main content
Glama

Locate moments in a video

find_moments

Search videos for ranked moments that match a natural-language description, with optional time-range and result limits to pinpoint relevant segments.

Instructions

Find ranked segments matching a description. Local files are uploaded to Google for processing; this call is billed to the user's API quota.

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": {
      "source": "<source>",
      "description": "<description>"
    },
    "name": "find_moments"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNonormal
sourceYes
refreshNo
descriptionYes
end_secondsNo
max_resultsNo
start_secondsNo

Output Schema

NameRequiredDescriptionDefault
cacheNo
modelYes
usageNo
detailYes
momentsNo
warningsNo
searched_rangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does add two genuinely valuable facts — local files are uploaded to Google, and the call is billed to the user's API quota — but it omits permission/auth needs, whether results are cached, what refresh actually re-runs, and how the video source is processed.

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 the tool's function, then the two operational caveats. Every clause carries information; there is no padding or redundancy.

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

Completeness3/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 values need not be described, and the cost/privacy warning covers an important non-obvious behavior. However, for a 7-parameter tool with zero schema coverage and no annotations, the definition leaves too much of the calling contract unstated to be considered complete.

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% across 7 parameters, so the description must compensate and largely does not. The only indirect hints are "matching a description" (the description parameter) and "local files are uploaded" (the source parameter); start_seconds, end_seconds, max_results, detail, and refresh are left entirely unexplained.

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?

"Find ranked segments matching a description" gives a specific verb (find) and a specific result shape (ranked segments), which is more informative than the title alone. It stops short of contrasting itself with siblings like analyze_video or extract_frames, so the agent must infer the boundary.

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?

No statement of when to use this tool versus analyze_video, video_info, or extract_frames, and no prerequisites (e.g. video length limits, supported source formats). The only implied usage is that a natural-language query drives the search, which the agent could have guessed from the name.

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

Deploy Server

Other Tools