Simpler.Asia

video.export_cancel

Stop a video export that is queued or rendering. The job ends as failed with "Cancelled by user.", anything it charged is refunded, the render stops, and any partial file is deleted. Cancelling a job that already finished or failed changes nothing (cancelled: false), so a repeat is safe. Refuses an unknown job (SIMPLER_STUDIO_EXPORT_JOB_NOT_FOUND): video.export_create returns job ids. Refuses a read-only connection (SIMPLER_MCP_SCOPE_READONLY): connect again with the 'mcp' scope. 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_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The export job (vx_...) to stop.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false, so the description carries the full burden and does: refunds charges, stops the render, deletes the partial file, sets the job to failed with a fixed message, and is idempotent on terminal jobs. It also names the two error codes (JOB_NOT_FOUND, SCOPE_READONLY) with the remedy for the latter, and says 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?

Five short sentences, front-loaded with the action and condition, then consequences, idempotency, errors and cost. Every sentence supplies information the agent needs (refund, file deletion, repeat safety, auth scope, cost) and none repeats the schema or title.

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 one-parameter mutation with no output schema, it covers the outcome (failed status, refund, partial file deletion), repeat-call behavior, failure modes with error codes, the scope fix, and provenance. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds provenance the schema lacks: job ids come from video.export_create and an unknown id yields SIMPLER_STUDIO_EXPORT_JOB_NOT_FOUND. That tells the agent how to obtain job_id and what a bad value does, which is meaningful beyond the single string property.

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 (stop/cancel a video export) and narrows the scope to jobs that are 'queued or rendering'. It also names the sibling video.export_create as the source of job ids, so the agent can place it among export, export_create and export_delete without opening schemas.

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?

Explicitly says when to use it (queued/rendering jobs) and when it is a no-op (already finished or failed, returns cancelled: false), which is effectively an exclusion. It does not compare against the other export siblings such as video.export_delete, so routing between cancel and delete is left implicit.

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?