BlitzReels Video Editor

List Exports

exports_list

Read-onlyIdempotent

List exports with render status and progress. Completed exports include a signed download URL. Pass exportId to return one export.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum exports to return when exportId is absent (1-50).
`offset`	No	Export offset when exportId is absent.
`exportId`	No	Return only this export, including its signed download URL when the render is complete. UUID string.
`projectId`	No	Filter exports by project ID. UUID string.
`workspaceId`	No	Optional workspace ID when projectId is not provided. Defaults to the user's default workspace. UUID string.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bounds`	Yes
`exports`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context beyond annotations: render status/progress and the presence of signed download URLs on completed exports. This informs the agent about the data shape and what to expect, without contradicting annotations.

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 two concise sentences with no filler. It front-loads the primary action and then adds the key differentiator (single export via exportId). Every word earns its place.

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?

Given the tool's low complexity, rich annotations, complete parameter schemas, and presence of an output schema, the description is sufficiently complete. It covers what the tool does, the main data included (status/progress, signed URLs), and the single-record mode. No additional context is necessary.

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%, with each parameter clearly explained. The description adds no new information about parameters beyond saying 'Pass exportId,' which the schema already documents. This meets the baseline of 3 when the schema carries the parameter-semantics burden.

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 clearly states the tool's purpose: 'List exports with render status and progress.' It also distinguishes two modes — listing all exports vs. returning one by exportId — which separates this from sibling tools like exports_start. The verb 'List' and resource 'exports' are specific and unambiguous.

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?

The description provides clear usage context: it lists exports with status/progress and notes that completed exports include signed download URLs. It also instructs when to pass exportId to retrieve a single export. While it does not explicitly name alternatives or exclusions, the single-vs-list distinction serves as effective usage guidance.

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

All BlitzReels Video Editor tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0

Disambiguation3/5

Most tools use clear domain prefixes, but several boundaries are fuzzy: clips_get and clips_manage both expose clip/export status, and update_timeline_clip overlaps with timeline_edit_apply for trim/duration changes. Detailed descriptions mitigate this, but an agent could still select the wrong tool for clip inspection or timeline edits.

Naming Consistency3/5

All names are snake_case and mostly readable, but the server mixes verb-first names (add_text_overlay, delete_timeline_items, update_timeline_clip) with noun-first domain-action names (clips_create, generation_*_create, media_import_*). The domain-prefix pattern dominates, yet the inconsistent verb placement makes the convention only partially predictable.

Tool Count1/5

58 tools is far beyond the 25+ threshold and matches the rubric's 50+ extreme-mismatch example. Even though the domain is broad, this surface would be easier for an agent to navigate if split into focused servers for media, generation, timeline editing, clips, and workflows.

Completeness3/5

Core video-editing flows are well represented: project creation/inspection, timeline item editing/deletion, media import/upload, AI generation, exports, and clips. However, lifecycle gaps remain—no project update/delete, no media asset deletion, no delete for characters or story kits, and no export cancellation—so some user requests will dead-end.

Resources

Need Help?