Skip to main content
Glama

Delete audio files

delete_audio
DestructiveIdempotent

Permanently delete audio files by media ID. Only call after the user explicitly asks; this cannot be undone. IDs that are not audio files are skipped.

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": {
      "ids": "<ids>"
    },
    "name": "delete_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMedia IDs of the audio files to delete, from list_audio or generation outputs.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
deleted_idsYesMedia IDs that were deleted. Skipped IDs are left out.

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?

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the description earns credit for what it adds: a permanence warning ('this cannot be undone') and partial-failure semantics ('IDs that are not audio files are skipped'). The skip behavior in particular is real operational context an agent cannot infer from the annotations.

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 short sentences, each doing distinct work: what it deletes, the consent gate plus irreversibility, and the skipped-ID edge case. The destructive consequence is front-loaded rather than buried.

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 destructive single-purpose delete tool with rich annotations, a fully documented schema, and an output schema, the description covers the risks an agent must weigh: permission gating, irreversibility, and behavior on non-matching IDs. Return-value detail is correctly left to the output schema.

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% and both parameters carry their own descriptions, including sourcing guidance ('from list_audio or generation outputs') for ids. The description adds no additional meaning about parameter format or limits, so the baseline 3 is appropriate.

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 plus resource plus identifier: 'Permanently delete audio files by media ID.' That immediately separates it from delete_images, delete_videos, and delete_brand, 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 Guidelines4/5

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

Gives a clear gating condition — 'Only call after the user explicitly asks' — which is exactly the guidance needed for an irreversible operation. It does not name a rollback or alternative tool (e.g. what to do instead if the user is unsure), so it falls just short of explicit alternatives.

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