Skip to main content
Glama

playhead

Get the current timeline timecode or move it to a specified timecode, and return the video item at that position.

Instructions

Get the playhead timecode of the current timeline, or move it to timecode. Also returns the video item under the playhead.

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

Input Schema

NameRequiredDescriptionDefault
timecodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false, which leaves ambiguous whether the tool always mutates. The description resolves this by making the mutation conditional on `timecode` being supplied, and it discloses a return value beyond the annotations (the video item under the playhead). It does not mention that the read branch is side-effect free or how the returned item is shaped.

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?

Two tight sentences with the primary function front-loaded and the return-value note appended. Every clause carries information, though the second sentence ('Also returns...') is slightly tacked on rather than integrated into the flow.

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 single-optional-parameter tool with no output schema, the description covers the core operation, the conditional read/write behavior, and the fact that an item is returned. The remaining omissions — timecode format and the structure of the returned video item — are modest given the tool's simplicity.

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 coverage is 0% for the single `timecode` parameter, so the description must carry the meaning — and it does partially, by indicating the parameter is the target position for moving the playhead and that its absence means a read. It adds no format guidance (timecode string vs frames vs seconds) or null-handling detail, leaving a real gap.

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 states a specific resource (the playhead timecode of the current timeline) and both modes of operation: read the timecode or move it. The term 'playhead' uniquely identifies the concern, so it is readily separable from siblings like insert_audio_at_playhead or add_markers. It stops short of explicitly naming any sibling it is distinct from.

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 implied by the get-or-set phrasing: supply `timecode` to move, omit it to read. There is no explicit statement of when-not to use it, no prerequisites, and no reference to the sibling tools that depend on playhead position (e.g. insert_audio_at_playhead), so the agent must infer the surrounding workflow.

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