Skip to main content
Glama

Get Full Clip Info

get_full_clip_info
Read-onlyIdempotent

Retrieve exhaustive details for a timeline clip, including all effect property values, source media, markers, speed, metadata, and proxy status, to inspect and troubleshoot edits.

Instructions

Get exhaustive information about a specific clip: all effects with every property value, source media details, footage interpretation, metadata, markers, speed, enabled state, color label, linked clips, and proxy status.

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": {
      "node_id": "<node_id>"
    },
    "name": "get_full_clip_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYesNode ID of the clip on the timeline
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's job is lighter. It usefully discloses the wide scope of the returned payload (effects, markers, proxy state), but says nothing about why a pure read tool accepts expected_cep_target / expected_project_path guards or how those preconditions fail – behavior the agent would otherwise need to discover from the schema.

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?

A single front-loaded sentence that puts the verb and scope first and then spends its words on the return payload rather than filler. The long enumeration is dense but every item is information an agent would otherwise have to query for.

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?

An output schema exists, so return-value documentation is not needed, and the annotations cover the safety profile; the description supplies the payload scope. The only real gap is unexplained guard parameters, which are unusual for a read-only tool and are left entirely to the schema.

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 100%, so per the rubric the baseline is 3. The description contributes nothing parameter-specific – it never mentions node_id or the expected_* guard objects, leaving all parameter meaning to the schema.

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 resource ('exhaustive information about a specific clip') and enumerates exactly what is returned: effects with property values, source media, footage interpretation, metadata, markers, speed, enabled state, color label, linked clips, proxy status. This breadth implicitly separates it from narrower siblings like get_clip_properties or get_qe_clip_info, but no sibling is named explicitly.

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 word 'exhaustive' – an agent can infer this is the heavyweight full-dump option versus targeted getters – but the description never states when to prefer it over get_clip_properties, get_qe_clip_info, or get_item_info, nor any cost/payload caveat for a comprehensive read.

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