Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Check the export

get_export
Read-onlyIdempotent

[read] Read the project's latest export, or the one named: its status (queued, rendering, done, failed or stopped) and progress. Use after export_video, with wait_seconds 45, until status is done or failed. When done, hand over download_url: public and signed, it works for 3 days; call again for a fresh one. Not for starting an export (use export_video). Returns render_id, status, progress, watermarked; when done download_url, expires_at, size_bytes, duration_seconds, width, height; when failed error. Related: export_video, export_captions, get_social_state. 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": "get_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoMany exports at once, max 20, each with this tool's fields; fields beside it are defaults.
render_idNorender_id from export_video. Default: the project's latest export.
project_idYesThe AskEditor project this acts on (from list_projects).
wait_secondsNoWait up to this long (0–45 s) for the export to finish before answering. Default 0: answer at once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses the status lifecycle, polling behavior, signed download_url validity, refresh behavior, and detailed return fields. It also clarifies that the download_url is public and expires after 3 days, which is valuable operational context.

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?

The description is front-loaded with the core read action and usage constraints, then compactly covers return values and related tools. There is no filler, and the density is justified because there is no output schema.

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?

With no output schema, the description supplies the important return fields and status-dependent behavior. It also covers download_url expiry, failure errors, and the recommended polling workflow, leaving no major operational gap.

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 description coverage is 100%, so parameter meanings are already well documented. The description contextualizes wait_seconds as a polling mechanism, but it does not mention the batch items parameter or add much detail beyond what the schema already provides.

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 read operation: reading a project's latest export or a named export, including status and progress. It explicitly distinguishes this from starting an export by naming export_video as the alternative.

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?

It gives explicit workflow guidance: use after export_video with wait_seconds 45 until status is done or failed, and do not use it to start an export. It also explains what to do when done by handing over download_url.

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

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