Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

vast_delete_linear_media

Delete a VAST linear media by its ID to remove it from AdButler, cleaning up your video ad inventory.

Instructions

Delete a VAST linear media

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesVAST linear media ID
Behavior1/5

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

With no annotations, the description is the sole source of behavioral disclosure, but it only restates the action 'Delete' without any detail about permanence, cascading effects, permissions, or error behavior. This adds no value beyond the tool name itself.

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?

The description is a single, concise sentence with no unnecessary words. It is appropriately sized for a simple delete operation, though it is terse and lacks broader context. It does not waste space, earning a high score on conciseness.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It does not explain whether the deletion is permanent, what happens on errors, or any dependencies or side effects. The low complexity and single parameter limit the need for extensive context, but the description is still too minimal.

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 the parameter 'id' described as 'VAST linear media ID'. The tool description adds no additional parameter meaning, so the baseline score of 3 is appropriate since the schema already documents the parameter sufficiently.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and the specific resource ('VAST linear media'), which distinguishes it from sibling tools like vast_delete_non_linear_media. However, it lacks additional context such as the scope or implications of deletion, making it slightly below a top score.

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 provided on when to use this tool versus alternatives. It does not mention that this is for linear media specifically, nor does it explain when to prefer this over vast42_delete_linear or other related delete operations. There is no exclusions or context about prerequisites.

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