Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

vast42_delete_non_linear

Delete a VAST 4.2 non-linear media by providing its ID.

Instructions

Delete a VAST 4.2 non-linear media

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVAST 4.2 non-linear media ID
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys only that the tool deletes a resource, with no mention of irreversibility, permissions, side effects, or consequences to associated entities.

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?

The description is a single, front-loaded sentence that stays exactly on point. There is no redundant information or unnecessary elaboration, making it maximally concise and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with one well-documented parameter, the description is adequate to convey the core purpose. However, it lacks any usage context or behavioral details, and there is no output schema to clarify expected return values, leaving the agent with minimal guidance beyond the basics.

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 schema describes the single 'id' parameter as 'VAST 4.2 non-linear media ID' with 100% coverage. The description itself does not add new parameter semantics beyond reinforcing that the ID identifies the media to delete, so it meets the baseline but no more.

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 "Delete a VAST 4.2 non-linear media" clearly specifies the action (delete) and target resource (VAST 4.2 non-linear media). This distinguishes it from sibling delete tools like vast42_delete_linear or vast42_delete_ad, which target different resources.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives, such as the non-4.2 vast_delete_non_linear_media or other VAST 4.2 delete operations. There is no mention of prerequisites, exclusions, or conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adbutler/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server