Skip to main content
Glama

Delete video project

delete_video_project
DestructiveIdempotent

Deletes the video project and attempts to delete its completed output. Cannot be undone; confirm with the user first.

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

Input Schema

NameRequiredDescriptionDefault
idYesUnique ID of the video project. This value is returned by all of the POST APIs that create a video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 known. The description still earns credit for disclosing that output deletion is best-effort ('attempts') and for reinforcing irreversibility with an explicit confirmation instruction. It does not say what happens to the project record if output removal fails, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the destructive scope first and the confirmation caveat second; nothing is padded. It could be one clause shorter but no sentence is wasted.

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 destructive delete with full schema coverage and no output schema, this covers the essentials: what is destroyed, that it is irreversible, and that the user must be asked first. The only gap is the result of a partial failure when output deletion does not succeed.

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?

The single 'id' parameter is fully documented in the schema, including where the value comes from. The description adds no field-level meaning, which is the expected baseline when schema coverage is 100%.

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 ('Deletes') plus the exact resource ('the video project') and adds the extra scope detail that it also attempts to remove the completed output. The resource name alone separates it from delete_audio_project and delete_image_project, so an agent can pick the right sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one clear precondition — 'confirm with the user first' — which is genuinely actionable for a destructive call. It stops there: no guidance on when the project should be deleted rather than kept, and no mention of what to use if the goal is only to remove the output.

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.