Skip to main content
Glama

Cancel a video that has not started rendering

autoshort_cancel_video
DestructiveIdempotent

Cancels a video that has not started rendering and refunds any credits charged through the ledger, net of earlier refunds. Refused once rendering has started or for operator-fulfilled clips.

Instructions

Cancel a video that has NOT started rendering (status PENDING or DRAFT) and refund whatever it was charged, through the credit ledger (net of earlier refunds — never twice). Refused once rendering has started (CANNOT_CANCEL_STARTED) and for operator-fulfilled clips. A cancelled video never renders later. 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": {
      "videoId": "<videoId>"
    },
    "name": "autoshort_cancel_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it explains the refund flows through the credit ledger, is net of earlier refunds and never paid twice, that a cancelled video will never render later, that it is free, and which cases are refused. This is exactly the mutation/refund context an agent needs before calling.

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?

Two tight sentences with the eligibility constraint front-loaded and no filler. The nested parentheticals and em-dash qualifiers make it slightly dense to parse, but every clause carries real information.

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, the description covers eligibility, side effects (refund ledger, permanent non-rendering), cost, idempotency, and failure modes. Nothing essential for correct invocation 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?

Schema coverage is 0% for the single required parameter videoId, and the description never clarifies its format or where to obtain it (e.g., from autoshort_get_video or a generation response). With only one obvious parameter the gap is small, but the description does not compensate for the missing schema description.

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 ('Cancel a video') plus the exact precondition (NOT started rendering, status PENDING or DRAFT), which immediately distinguishes it from generate/publish siblings. An agent knows precisely what operation this performs.

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 gives both the when ('status PENDING or DRAFT') and the when-not ('Refused once rendering has started', 'operator-fulfilled clips') with the error code CANNOT_CANCEL_STARTED. It does not name an alternative tool for videos already rendering, so it stops short of full routing guidance.

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