Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

vast_create_non_linear_media

Create new VAST non-linear media for ad campaigns. Provide name, width, height, and MIME type to define the creative.

Instructions

Create a new VAST non-linear media

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesNon-linear media name
widthNoWidth in pixels
heightNoHeight in pixels
mime_typeNoMIME type
Behavior1/5

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

With no annotations, the description must disclose behavioral traits, but it only says 'Create a new VAST non-linear media'. It does not mention side effects, idempotency, required relationships (e.g., to a campaign or ad), or what response to expect. This is a significant transparency gap for a mutation tool.

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 sentence with no wasted words. It is front-loaded with the primary action and object. While minimal, it is not a tautology and avoids unnecessary verbosity.

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

Completeness1/5

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

The description is extremely sparse for a create operation with no output schema and no annotations. It fails to explain what 'non-linear media' is, what constraints or defaults apply, what the response contains, or how it relates to other VAST entities. An agent would have to infer most details from the schema and tool name.

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 input schema has 100% description coverage for its four parameters (name, width, height, mime_type), so the schema carries the semantic load. The description adds no additional meaning to these parameters, so a baseline score of 3 is appropriate.

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 ('Create') and the resource ('VAST non-linear media'), which distinguishes it from sibling tools like vast_list_non_linear_media or vast_update_non_linear_media. However, it does not elaborate on what non-linear media entails in this context.

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

Usage Guidelines1/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 such as vast42_create_non_linear or vast_create_linear_media. There is no mention of prerequisites, use cases, or conditions that would make this tool the appropriate choice.

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