Skip to main content
Glama

seek

Jump to a specific video timestamp by providing seconds, enabling precise playback positioning for review, clipping, or instruction.

Instructions

Seek to a position in seconds

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": {
      "seconds": "<seconds>"
    },
    "name": "seek"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsYesPosition in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing: not whether playback continues or pauses after seeking, not what happens for out-of-range values, not whether the operation is instant or buffered. For a playback-control mutation this is a significant gap.

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?

One short front-loaded sentence with zero filler and the action plus unit stated immediately. It is efficient, though its brevity borders on under-specification rather than earned conciseness.

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?

The tool is simple (one fully-described parameter, no output schema, no nesting), so the description is minimally sufficient to call it. It nonetheless omits the playback-state behavior and any reference to the neighboring seek variants that an agent would need to choose correctly.

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?

The single parameter is fully documented in the schema ('Position in seconds'), so the schema already does the heavy lifting and the description's 'in seconds' merely restates the unit. No added meaning such as accepted ranges, negative offsets, or precision.

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

Purpose3/5

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

States a specific verb ('Seek') and unit ('seconds'), so the basic action is inferable, but it never names the resource being seeked in (current media? current file?) nor distinguishes itself from siblings like chapter_seek or seek_to_text.

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 when-to-use guidance at all. Given siblings such as chapter_seek and seek_to_text, an agent has no signal about when absolute seconds-based seeking is the right choice versus chapter- or text-based seeking.

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