Skip to main content
Glama

metadata_export

Export clip metadata to CSV for selected items or all media pool clips, making it available for review, reporting, and downstream workflows.

Instructions

Export clip metadata to CSV (all media pool clips if items not given).

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": "metadata_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only discloses the CSV output and default clip scope. It says nothing about whether an existing file at 'path' is overwritten, whether the write is reversible, what permissions are required, or what the tool returns on success or failure — significant gaps for a filesystem-writing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence that front-loads the action and output format, then adds the default-scope rule in a compact parenthetical. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter export tool with no annotations and no output schema, the description is under-specified: overwrite behavior, which metadata fields are included, and failure modes are all unstated. An agent could call it, but only by guessing at the risky parts.

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 0%, so the description must compensate, and it does explain the optional 'items' parameter (defaulting to all media pool clips), which is the more ambiguous of the two. The required 'path' parameter is left to its bare title with no note on expected format or extension, so the compensation is only partial.

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 the specific verb 'Export' with the resource 'clip metadata' and the output format 'CSV', which is more than the name alone conveys. It does not explicitly distinguish itself from siblings like timeline_export or project_export, so the agent must infer that this one is clip-scoped rather than timeline- or project-scoped.

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 parenthetical gives one clear usage rule — omit items to export all media pool clips — which tells the agent the default scope. However, there is no guidance on when to choose this over timeline_export, project_export, or quick_export, and no prerequisites (e.g., open project, disk permissions) are mentioned.

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