Skip to main content
Glama

Export

export
Destructive

Get the files of starred takes: one entry per output asset, as in download_asset (saved to the current directory over stdio, or a short-lived signed URL over HTTP), tagged with item and take_id. Give item (id, slug or @slug) for one item, else every item in the project is covered. Give take_id to export that take even if it is not starred (needs item). Takes that are not starred are skipped, so star first.

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": {
      "project": "<project>"
    },
    "name": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo
projectYes
take_idNo
overwriteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds real behavioral detail not in structured fields: files are written to the current directory over stdio or delivered as a short-lived signed URL over HTTP, and entries are tagged with `item` and `take_id`. The one gap is that the `overwrite` parameter and any file-collision behavior are never described, which matters for a destructive-flagged tool.

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?

Front-loaded with the core action and the download_asset comparison, then parameter rules, then the prerequisite. It is dense but mostly earned; the clause 'else every item in the project is covered' is slightly awkwardly phrased but carries necessary default behavior.

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 values need no explanation, yet the description still usefully summarizes the per-asset shape. Delivery mechanism, scoping defaults, and the starring prerequisite are all covered; only the overwrite/collision semantics are missing for a tool flagged destructive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 carry parameter meaning, and it does for three of four: `item` accepts id, slug, or `@slug`, `take_id` implies `item`, and `project` scoping is implied by 'every item in the project'. `overwrite` is left completely undefined despite defaulting to false on a destructive operation, which prevents a higher score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the files of starred takes'), defines the output shape ('one entry per output asset'), and distinguishes itself from the sibling download_asset by referencing it directly. An agent can tell exactly what this returns versus a single-asset download without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit branching rules are given: pass `item` for one item, omit it to cover the whole project, pass `take_id` to force-export an unstarred take (and it notes `item` is required for that). It also states the prerequisite 'Takes that are not starred are skipped, so star first', naming a real sibling action.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources