Skip to main content
Glama

get_position

Retrieve the saved playback position for a media file to resume watching from where you left off.

Instructions

Get saved playback position for a file

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": {
      "path": "<path>"
    },
    "name": "get_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely does not meet it. It does not say what is returned when no position has been saved (error, null, or zero), what units the position is in, or whether reading a position requires the file to be currently openable.

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 front-loaded sentence with zero filler and no redundancy. It is efficient, though it is terse enough that the brevity edges into under-specification rather than crispness.

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?

For a single-parameter read tool with no output schema, the description covers the core intent but leaves the return value's shape and units unexplained. An agent knows what to send but not exactly what to expect back, including the no-saved-position case.

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 100% and there is a single parameter whose description ('Path to the media file') is already complete. The description's phrase 'for a file' restates the schema rather than adding format details such as absolute vs relative paths, so the baseline of 3 applies.

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?

States a specific verb ('Get') and a specific resource ('saved playback position for a file'), which distinguishes it from live-state readers like get_status. It does not, however, acknowledge the obvious sibling save_position, so the get/save pairing must be inferred from the names.

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?

The word 'saved' implies this returns a persisted bookmark rather than the current live playback position, which is a useful implicit signal. There is no explicit when-to-use guidance, no mention of save_position as the counterpart, and no statement about behavior when nothing has been saved.

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