Skip to main content
Glama

Cancel a video

cancel_video
Destructive

Cancel a video that has NOT started rendering: a draft, a video still queued (PENDING), or one whose failed render is waiting for an automatic retry. The video ends as FAILED "Cancelled" and is never rendered. Credits are charged only after a render succeeds, so normally nothing had been charged; if the ledger holds a charge for it, exactly that is refunded (idempotent, never twice) and refundedCredits says how much. A video that is already rendering, finished, or a clip made straight from a prompt is refused (CANNOT_CANCEL_STARTED) and left untouched. Requires the "video:create" scope.

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": "cancel_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true and idempotentHint=false; the description goes far beyond by disclosing the terminal state (FAILED "Cancelled"), that no render occurs, the credit-ledger rule (refund exactly what was charged, never twice, surfaced as refundedCredits), and the required "video:create" scope. The 'refund is idempotent' note sits alongside idempotentHint=false but refers to the ledger operation, not the call, and is explained rather than contradictory.

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?

Eligibility is front-loaded in the first sentence, refusals and error code follow, and credit behavior plus scope close it out. Dense but zero filler; every sentence carries decision-relevant 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?

No output schema exists, and the description covers the one return value that matters (refundedCredits), the terminal state, the failure code, and the auth scope. Nothing an agent needs to invoke this single-parameter destructive tool 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 description coverage is 0% and videoId has no type detail, but the description makes clear the ID must reference a video in a cancellable state and what happens to that video. It does not state an ID format, which the schema also omits, so a small gap remains.

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) and immediately bounds it: only drafts, PENDING-queued videos, or failed renders awaiting automatic retry. The eligibility window makes it distinguishable from render/publish/delete operations without opening any schema.

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?

Explicitly names the states where it applies (draft, queue, failed retry) and the states where it must not be used (already rendering, finished, prompt-clip), including the error code CANNOT_CANCEL_STARTED returned in refusal cases. An agent can decide pre-call whether the target is cancellable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources