Skip to main content
Glama

Cancel a queued Playground media job

playground_media_job_cancel
DestructiveIdempotent

Cancel one queued agent image or video job and release its credit hold. A processing provider job cannot be cancelled by this tool. Requires project edit access.

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": {
      "projectId": "<projectId>",
      "dispatchId": "<dispatchId>"
    },
    "name": "playground_media_job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
dispatchIdYesDispatch receipt ID returned by generation or media_jobs_list; reuse it to check the same job.

Output Schema

NameRequiredDescriptionDefault
errorYes
jobIdNo
statusYes
dispatchIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, it discloses two valuable traits: the side effect of releasing a credit hold, and the state restriction that in-flight provider jobs are not cancellable. Annotations already cover destructive/idempotent semantics, and nothing here contradicts them. It is silent on what happens to any partial output from the cancelled job, which would have earned a 5.

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?

Three short sentences, each carrying distinct information: what it does, what it excludes, and what it requires. The scope constraint is front-loaded and there is no redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two fully documented parameters, an output schema, and annotations covering safety semantics, the description supplies the remaining needed context: preconditions, side effects, and state constraints. The only gap is guidance on recovery when cancellation is rejected for a processing job.

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 both projectId and dispatchId well documented in the schema itself (including where dispatchId comes from). The description adds no format or disambiguation detail beyond that, so the baseline applies.

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 opens with a specific verb and resource ('Cancel one queued agent image or video job') and immediately narrows scope to queued jobs only. This distinguishes it cleanly from siblings like playground_media_job_get and playground_media_jobs_list without needing their 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?

It states a clear negative condition ('A processing provider job cannot be cancelled by this tool') and a prerequisite ('Requires project edit access'), which is meaningful routing guidance. It stops short of naming the alternative to use instead when a job is already processing, leaving the agent to infer it from siblings.

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.