Skip to main content
Glama

Create export

create_export
Destructive

Generates a production document and returns a download link. kind=report gives the full production report as PDF, Word (docx) or spreadsheet (xlsx); format=saturation gives a JSON bundle of Saturation API requests that rebuilds the budget in the user's own Saturation workspace; kind=breakdown gives the breakdown sheets (PDF only). Use it when the user wants the plan as a file they can keep or send to the crew, a financier or a festival. Exports are the professional documents of the production (the top sheet and report as PDF, Word or spreadsheet, the Saturation budget bundle; the schedule reaches Movie Magic Scheduling as a Final Draft file from the app): they generate once the production is unlocked (Production, US$79 per production, or the Studio slate plan).

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_id": "<project_id>"
    },
    "name": "create_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoreport for the full production report, breakdown for the breakdown sheets (PDF only).report
formatNopdf, docx, xlsx or saturation.pdf
project_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, but the description frames the operation only as generating a document and returning a download link, with no explanation of what may be overwritten, deleted, or otherwise affected. It does add useful context about the production needing to be unlocked via a paid plan or Studio slate, but the destructive behavior itself remains undisclosed.

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 purpose and primary usage condition are front-loaded, and most sentences carry useful information. The final sentence is dense and repeats some export-type detail by restating the professional documents covered, though it also adds the important unlock prerequisite.

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?

With an output schema present, the description does not need to explain return values, and it covers the key invocation details: output types, format combinations, and the production-unlock prerequisite. The main gap is that it does not describe the destructive side effect signaled by annotations.

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?

The description adds meaningful semantics beyond the schema by mapping kind=report to PDF/docx/xlsx, format=saturation to a JSON bundle of Saturation API requests, and kind=breakdown to PDF-only breakdown sheets. The project_id parameter is not described, but its meaning is obvious from the name and context.

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?

The description states a specific verb and resource: it generates a production document and returns a download link. It goes further by explaining what each kind/format produces and distinguishes schedule delivery through the app rather than this export tool.

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

Usage Guidelines4/5

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

It gives a clear when-to-use condition: when the user wants the plan as a file to keep or send to crew, a financier, or a festival. It also implicitly excludes schedule delivery by noting that the schedule reaches Movie Magic Scheduling from the app, though it does not name an explicit in-app alternative such as get_budget.

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