Skip to main content
Glama

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

Delete an image

pixverse_delete_image
DestructiveIdempotent

Delete one image from its PixVerse account by image_id (from pixverse_create_image, pixverse_get_image or pixverse_list_images). Videos and music videos are deleted with pixverse_delete_video. Cannot be undone. DELETE /images/{image_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": {
      "image_id": "<image_id>"
    },
    "name": "pixverse_delete_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_idYesThe image_id, e.g. user:12345-pixverse:you@example.com-image:123456789 (it names the account).

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 readOnlyHint=false, so the safety profile is largely structured data. The description adds the irreversibility warning ('Cannot be undone') and account scoping, which is real but modest context beyond the annotations; it says nothing about side effects on videos derived from the image or about the response.

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 tight sentences plus an endpoint, front-loaded with the action and scope, with no filler. Every clause carries a distinct decision-relevant fact: what it deletes, what identifier to supply, and which sibling handles the rest.

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 one-parameter, annotation-rich, no-output-schema tool this covers action, identifier provenance, alternative route and permanence. Minor gaps remain around follow-on effects and any precondition that the image be unreferenced, but nothing essential for a correct call 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 100%, so the baseline is 3, but the description earns more by naming the producing tools for image_id and noting that the id encodes the owning account. That provenance is meaning the schema does not convey.

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 ('Delete one image from its PixVerse account') scoped by image_id, and explicitly names the non-overlapping sibling for other media types ('Videos and music videos are deleted with pixverse_delete_video'). An agent can distinguish it from the sibling delete tool without opening either schema.

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?

Gives a clear routing rule for non-image media and tells the agent where the identifier comes from (pixverse_create_image, pixverse_get_image, pixverse_list_images), which closes the main prerequisite loop. It stops short of stating exclusions or preconditions such as whether the image can be deleted while a job references it.

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