Skip to main content
Glama

get_clip

Read-only

Retrieves a media pool clip’s properties, metadata, markers, flags, audio mapping, mattes, and timeline data. Specify sections to limit which details are returned.

Instructions

Everything about a media pool clip. sections (default all): properties, metadata, third_party_metadata, markers, flags, mark_in_out, audio_mapping, media_id, mattes, timeline.

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": {
      "clip": "<clip>"
    },
    "name": "get_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
sectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a safe, read-only, non-open-world operation. The description adds useful scope behavior by listing available sections and stating the default is all, but it does not mention output shape, error behavior, or performance implications.

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 very compact and front-loads the resource scope before listing sections. The phrasing is slightly terse and the sentence structure around 'sections' is not fully polished, but there is little wasted wording.

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 simple read tool this is mostly adequate: it identifies the resource and the selectable sections. However, with no output schema and no schema descriptions, the definition leaves the required clip identifier undocumented and does not explain the response structure.

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 description coverage is 0%, so the description must compensate. It does enumerate the accepted section names and the default-all behavior, but it says nothing about the required 'clip' parameter's meaning or accepted format.

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 clearly states the resource ('media pool clip') and enumerates the data sections returned. It does not explicitly distinguish this tool from siblings such as get_item or get_markers, so it falls short of a 5.

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?

The description gives no when-to-use guidance, no alternatives, and no exclusions. 'sections (default all)' implies a usage pattern but does not explain when a caller should use this tool versus related retrieval tools.

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