AskEditor

Export the final video

export_video

[write] Start the project's final export with set_export_settings' settings, on AskEditor's servers. Free includes 3 of those in all; after them the film is made in the person's editor beside the chat, on their computer, then uploaded (open it first). Use when the edit is finished and the person wants the file. Runs up to ~20 min; a call while one runs returns it. Refuses an empty timeline. Not for one graphic (use render_asset). Returns render_id, status, progress, watermarked and the settings used. Call get_export with wait_seconds 45 until status is done or failed. Related: set_export_settings, get_export, export_captions. Full docs: load_skill with tools: [name].

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

Input Schema

Name	Required	Description	Default
`project_id`	Yes	The AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the read/write/idempotency profile; the description goes far beyond them, disclosing server-side vs. local rendering after the free quota, that the editor must be opened first, a ~20 min runtime, concurrent-call behavior, and a hard precondition (refuses an empty timeline). It also names the return fields, so the agent knows what to poll on.

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-loads the action and quota constraint, then usage, preconditions, and the polling recipe — every sentence carries information. Some phrasing is clumsy and run-on ("Free includes 3 of those in all", "made in the person's editor beside the chat"), costing a bit of readability.

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

Completeness5/5

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

No output schema exists, but the description enumerates the returned fields (render_id, status, progress, watermarked, settings) and explains the polling loop, preconditions, and failure states. Nothing an agent needs to invoke and follow up correctly is missing.

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?

Only one parameter (project_id) and schema coverage is 100%, so the schema already fully documents it. The description adds no format or sourcing detail beyond the schema's "from list_projects" note, so this sits at the baseline for fully-covered schemas.

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 ("Start the project's final export") with the settings source named, and explicitly excludes the nearest sibling: "Not for one graphic (use render_asset)." An agent can distinguish this from render_asset, get_export, and set_export_settings without opening any 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?

Gives the triggering condition ("Use when the edit is finished and the person wants the file"), the exclusion with an alternative (render_asset), and the follow-up procedure ("Call get_export with wait_seconds 45 until status is done or failed"). Alternatives and when-not are both explicit.

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

All AskEditor 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?