Skip to main content
Glama

get_moment

Retrieve a transcript slice, up to 3 frames with OCR text, and wall-clock range for a specified time segment. Use for triage to get quote, screenshot, and on-screen text in one call.

Instructions

The "one remark" evidence bundle: transcript slice + up to 3 unique frames + their OCR text + the wall-clock range for [start_ms, end_ms], in a single call. This is the workhorse for triage: one call per finding gives you the quote, the screenshot, and the on-screen text. When NOT to use: broad exploration (get_transcript / get_frames) or keyword lookup (search). Examples:

  • get_moment(job_id="...", start_ms=83000, end_ms=97000) — full evidence for the remark at 1:23-1:37

  • segment seq 12 spans t0_ms=83210, t1_ms=96800 → get_moment(job_id, 83210, 96800)

  • pad ±2000 ms around the spoken range — narrators react to things already on screen

  • triage loop: for each candidate finding, exactly one get_moment call → quote + frame + OCR

  • user: "what was I showing when I said 'this button is broken'?" → search first, then get_moment at the hit

  • opening context of a meeting: get_moment(job_id, 0, 15000)

  • response includes the t_wall range when known → quote it in bug reports for log correlation

  • audio-only job → returns the transcript slice plus a no-frames note (that is expected)

  • anti-example: whole-video summary → get_transcript(format="text"), not a chain of get_moments

  • anti-example: need more than 3 frames of a range → get_frames(start_ms=..., end_ms=..., max_frames=6)

  • keep ranges under ~30 s; a 5-min "moment" dilutes the bundle and wastes tokens

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_msYes
job_idYes
start_msYes
Behavior5/5

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

No annotations are provided, but the description fully discloses the tool's behavior: it returns a transcript slice, up to 3 unique frames with OCR text, and the wall-clock range. It also notes audio-only job behavior (returns transcript slice plus a no-frames note) and recommends keeping ranges under ~30 seconds, which goes beyond basic read-only semantics.

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?

The description is front-loaded with the core purpose and provides structured examples and anti-examples. However, it is somewhat lengthy with many examples; while informative, it could be tightened slightly without losing clarity. Still, it earns a 4 for being well-organized and adding value.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return bundle in detail, covers edge cases (audio-only), and provides usage patterns and constraints (max 3 frames, keep under ~30s). It equips an agent to know exactly what to expect and how to use the tool effectively, making it very complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. While it does not formally describe each parameter, the examples (e.g., 'get_moment(job_id="...", start_ms=83000, end_ms=97000)') and context ('full evidence for the remark at 1:23-1:37') make the parameter meanings clear. The parameter names are self-explanatory, and the description adds practical usage patterns, meriting a 4.

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?

The description clearly states that get_moment retrieves a 'moment' bundle (transcript slice + up to 3 frames + OCR + wall-clock range), and distinguishes from siblings by explicitly stating when not to use the tool (broad exploration via get_transcript/get_frames, keyword lookup via search).

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

Usage Guidelines5/5

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

The description provides explicit when-to-use (triage, one call per finding), when-not-to-use (broad exploration, keyword lookup), and lists alternative tools. It also includes detailed examples and anti-examples, giving clear guidance on selecting this tool over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/korovin-aa97/talkthrough-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server