Skip to main content
Glama

clip_info

Retrieves properties and metadata for a media pool clip, including codec, resolution, frame rate, timecode, path, markers, flags, in/out marks, audio mapping, and transcription availability.

Instructions

Everything about one media pool clip: properties (codec, res, fps, TC, path…), metadata, markers, flags, in/out marks, audio mapping and transcription availability.

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": {
      "item": "<item>"
    },
    "name": "clip_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the breadth of returned data, which is useful, but never states that this is a read-only operation, what happens when the item is invalid or missing, or whether the call is expensive on large clips.

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 a parenthetical example list; no filler. Slightly dense enumeration but every element names a real returned field.

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?

No output schema and no annotations, so the description must establish both the item parameter contract and the operation's safety profile, and it does neither. It is adequate on scope of returned data but incomplete on how to call it correctly.

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?

There is one parameter, 'item', with 0% schema description coverage, and the description says nothing about it. It is unclear whether 'item' is a clip name, a unique ID, an index, or a pool path object. That is the single largest ambiguity in the definition.

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 resource (one media pool clip) and enumerates what it returns (properties, metadata, markers, flags, in/out marks, audio mapping, transcription availability). This differentiates it reasonably from narrower siblings like clip_properties or markers, though it never uses an explicit verb such as 'return' or 'retrieve'.

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 enumeration implies the use case: fetch comprehensive info about a single clip rather than a subset. There is no explicit when-to-use versus when-not guidance and no differentiation from clip_properties or markers, which appear to overlap on the same clip fields.

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