PostNitro

Delete Audio File

postnitro_delete_audio

DestructiveIdempotent

Permanently delete an audio file from the workspace, including the stored file. This cannot be undone — confirm with the user first.

An audio file still referenced by a scheduled post is refused (the reel would lose its soundtrack at publish time); remove it from those posts first. Videos already rendered to MP4 keep their audio, since the track is baked into the file.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`audioId`	Yes	The audio ID to delete (get from postnitro_list_audio)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	Yes	Confirmation message
`success`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes beyond the annotations (destructiveHint=true, idempotentHint=true) by explaining irreversibility, the requirement to confirm with the user, the refusal behavior for audio in scheduled posts, and the fact that rendered MP4s keep their audio. No contradictions with 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?

Two concise paragraphs: the first states the action and irreversibility; the second covers two important edge cases. No redundant words, and the critical information is front-loaded.

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?

The description covers all key operational aspects: irreversibility, confirmation need, dependency on scheduled posts, and behavior with rendered videos. With an output schema present and the simplicity of one parameter, nothing essential is missing for an agent to invoke it correctly.

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 description coverage is 100% — the audioId parameter has a clear description ('The audio ID to delete (get from postnitro_list_audio)'). The tool description adds no extra parameter semantics, but the schema already handles it, so 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?

The description clearly states the tool's function: 'Permanently delete an audio file from the workspace, including the stored file.' It specifies the verb (delete), resource (audio file), and scope (workspace and stored file), distinguishing it from sibling tools like postnitro_delete_scheduled_post.

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?

It gives practical guidance: confirm with the user first due to irreversibility, and warns that audio referenced by scheduled posts is refused, requiring removal from those posts first. It doesn't explicitly name alternatives, but none exist for this operation; the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PostNitro tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools are clearly separated by verb and noun (generate_carousel vs generate_image vs generate_video, import_* vs generate_*). The generic convenience names like generate_and_wait and import_and_wait are slightly ambiguous, but their descriptions and the _wait/_schedule suffixes make them distinguishable.

Naming Consistency4/5

All tools share the postnitro_ prefix and snake_case verb-first convention. A few compound names (generate_and_schedule, import_and_wait) break the strict verb_noun pattern, but the convention is otherwise consistent and predictable.

Tool Count2/5

With 35 tools, the surface exceeds the rubric's 25+ 'too many' threshold. Many entries are convenience wrappers (_wait, _and_schedule) around the same core operations and could be consolidated to reduce overload.

Completeness4/5

The domain is well covered: generation, import, output retrieval, scheduling, brands, social accounts, audio, templates, presets, and defaults. Minor gaps remain (no delete_brand, no upload/connect for audio/social accounts), but those are largely external or non-critical.

Resources

Need Help?