Montik

Export projects

export_projects

Export several projects at once (e.g. this project and its variants), each to its own file. Returns one job per project; check with export_status in each project.

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": {
      "projectIds": "<projectIds>"
    },
    "name": "export_projects"
  }
}

Input Schema

Name	Required	Description
`height`	No
`quality`	No	default fast
`loudness`	No	target LUFS for the mix (default -14 for social; null = untouched)
`projectId`	No	Project to act on (default: the open one)
`approvalId`	No	Only after needs_approval: the id it gave, once the user said yes
`projectIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already establish that this is a non-read-only but non-destructive operation. The description adds useful async behavior by noting that one job is returned per project and status must be checked per project, but it omits the approval flow implied by the approvalId parameter.

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?

Two compact sentences, front-loaded with the core action and followed by the relevant follow-up behavior. There is no unnecessary 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?

The description covers the essential export-and-check flow for a batch operation, but it leaves notable gaps around approval requirements, parameter behavior, and differentiation from sibling export tools. With no output schema, more detail about job results would help.

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 67%, with descriptions for quality, loudness, projectId, and approvalId. The description reinforces that projectIds refers to multiple projects, but it adds little meaning for height, quality, loudness, or the relationship between projectId and projectIds.

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 states a specific verb and resource: exporting several projects at once, each to its own file. This distinguishes it reasonably well from single-item export siblings, though it does not explicitly name export_video or export_takes as alternatives.

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 description implies usage for multiple projects and tells the agent to check export_status afterward, but it does not explain when to choose this over export_video, export_takes, or other export tools.

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

All Montik tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?