Skip to main content
Glama

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

Delete a video

pixverse_delete_video
DestructiveIdempotent

Delete one video from its PixVerse account by video_id (from a create tool, pixverse_get_video or pixverse_list_videos); music videos too (same video_id). Images: pixverse_delete_image. Cannot be undone. DELETE /videos/{video_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": {
      "video_id": "<video_id>"
    },
    "name": "pixverse_delete_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe video_id, e.g. user:12345-pixverse:you@example.com-video:123456789 (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried; the description still adds real context by stating irreversibility explicitly and disclosing the underlying DELETE /videos/{video_id} call. It does not describe what happens to dependent resources or the response, so it falls short of 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?

One dense, front-loaded sentence plus two short fragments; every clause carries operational information (id provenance, music-video coverage, image alternative, irreversibility, endpoint). No filler.

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 single-required-parameter destructive tool with full schema documentation and no output schema, nothing an agent needs in order to invoke it correctly is missing. Provenance, scope, and the destructive consequence are all covered.

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 schema already documents the video_id format with an example, so the baseline is 3. The description adds meaning beyond that by telling the agent where to obtain the id and that the id itself identifies the account, which matters in a multi-account tool set.

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 (delete) and resource (one video) scoped to 'its PixVerse account', and explicitly notes music videos are handled by the same tool while images are not. An agent can distinguish it from pixverse_delete_image, pixverse_get_video, and pixverse_list_videos 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?

Names the concrete sources for the required id (create tools, pixverse_get_video, pixverse_list_videos) and routes the image case to the sibling pixverse_delete_image. The 'cannot be undone' warning effectively communicates the decision boundary for this destructive call.

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