Simpler.Asia

video.export_delete

Delete a finished video export's files (the mp4 and any SRT) now, before the automatic deletion 30 days after the export finished. Every download link for that job stops working at once; the job record stays, so the daily export limit still counts it. Refuses a job that is still rendering (SIMPLER_STUDIO_EXPORT_DELETE_ACTIVE): stop it with video.export_cancel, or follow it to the end with video.export, then delete it. Refuses an unknown job (SIMPLER_STUDIO_EXPORT_JOB_NOT_FOUND): video.export_create returns job ids. Free.

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": {
      "job_id": "<job_id>"
    },
    "name": "video.export_delete"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The export job (vx_...) whose files to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the bare readOnlyHint=false annotation: discloses that every download link breaks immediately, that the job record survives so the daily export limit still counts it, and names the exact error codes (SIMPLER_STUDIO_EXPORT_DELETE_ACTIVE, SIMPLER_STUDIO_EXPORT_JOB_NOT_FOUND) and that the call is free.

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?

Front-loads the destructive effect, then consequences, then refusal modes, then cost. Dense but every clause carries operational information; nothing is padding.

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?

For a single-parameter, no-output-schema destructive tool, the description covers impact, irreversibility, side effects on quota, prerequisites, and recovery alternatives — everything an agent needs to call it safely.

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?

Schema coverage is 100% so the schema already defines job_id, but the description adds real value by telling the agent where job ids come from (video.export_create) and tying the required parameter to the failure mode it triggers.

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 ('Delete a finished video export's files') plus the exact artifacts affected (mp4 and any SRT), and it is clearly distinguishable from siblings like video.export_cancel and video.export, which it references by name.

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 explicit routing: for a still-rendering job use video.export_cancel or video.export, for unknown ids use video.export_create. It also explains the default path (waiting 30 days) to frame why this tool exists.

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

All Simpler.Asia 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?