Skip to main content
Glama

PixVerse MCP Server by useapi.net (third-party)

Stop tracking a running job

pixverse_cancel_job
DestructiveIdempotent

Stop tracking a running video, image, music or speech job (from pixverse_list_running_jobs) and free its slot on the account. It does not stop the job at PixVerse. 404 when the id is not running. Cannot be undone. DELETE /scheduler/{id}.

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": {
      "id": "<id>"
    },
    "name": "pixverse_cancel_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe running job's id, e.g. user:12345-pixverse:you@example.com-video:123456789.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is largely carried by structured data. The description still adds real value beyond that: the side effect is only local tracking removal, the remote job keeps running, a 404 signals a non-running id, and the effect is irreversible. Return shape is not described, and since no output schema exists that is a remaining gap.

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?

Four short sentences, front-loaded with the core action and immediately followed by the key limitation. Every sentence carries distinct information — scope, negative effect, error case, irreversibility, endpoint — with no restatement of the name or 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?

For a single-parameter mutation with no output schema, everything needed to invoke it correctly is present: id origin, the scope of the effect, and the failure condition. Only the response body on success is unspecified, which is minor given the description implies a bare DELETE-style acknowledgement.

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% and the single `id` parameter is fully documented with an example format, so the baseline is already high. The description adds provenance (the id comes from pixverse_list_running_jobs) and error semantics (404 on non-running ids), which is meaning beyond the schema.

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 gives a precise verb-and-resource pair: it stops *tracking* a running job of four possible media types and frees its account slot. The crucial disambiguation — 'It does not stop the job at PixVerse' — prevents the most likely misread and separates it from any job-cancellation expectation.

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 names the source of valid ids (pixverse_list_running_jobs) and states the failure condition ('404 when the id is not running'), which is exactly the context needed before calling. It does not name an alternative tool for the case where the user actually wants to halt the render, though it does state that no such effect occurs here.

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