Skip to main content
Glama

Singing Pet

Delete a video

delete_video
DestructiveIdempotent

Permanently delete one of this account's videos. Does not refund the credit it cost.

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

Input Schema

NameRequiredDescriptionDefault
video_idYesVideo id returned by create_singing_video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds two non-obvious consequences beyond that: permanence and that the spend credit is forfeited. It does not cover what happens when the id is invalid, whether deletion is blocked while a job is in flight, or whether the media is purged immediately versus soft-deleted.

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?

Two short sentences, zero filler, with the staking consequence (permanence) placed first and the secondary cost consequence after it. Nothing is repeated from the name or the schema.

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 one-parameter destructive tool with rich annotations and full schema coverage, this is sufficient: the agent knows what it destroys, that it is irreversible, and that it costs the user a credit. No output schema is present, and none is needed for a delete acknowledgement.

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 coverage is 100% with a single documented parameter that already states where the id comes from, so the schema does the heavy lifting. The only addition is the account-scoping phrase, which implies a video_id from another account will fail, but no format or validation detail is supplied.

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 ('Permanently delete ... videos') with the ownership scope made explicit ('one of this account's videos'), which cleanly separates it from the create/get/list siblings. The irreversibility qualifier is front-loaded rather than buried.

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 clear decision context — the operation is permanent and the credit is not refunded — which tells an agent to treat this as a last-resort action. It does not name any alternative (e.g. how to locate the video first, or whether a non-destructive option exists), so it stops short of explicit when/when-not routing.

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