Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

vast_list_media

List all VAST media (linear and non-linear) from AdButler, using offset and limit to manage result volumes.

Instructions

List all VAST media (linear and non-linear)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 100, max 100)
offsetNoPagination offset
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'List all VAST media' but omits that this is a read-only operation and that results are paginated via limit/offset. The word 'all' is potentially misleading because the schema has a default limit of 100, implying not all items are returned in a single call.

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, concise sentence that immediately conveys the tool's purpose. There is no superfluous information, and it is appropriately front-loaded.

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 listing tool with two optional parameters and no output schema, the description is mostly adequate, but it lacks important contextual details. It does not clarify pagination behavior, what fields are returned, or that 'all' is subject to the default limit. The lack of an output schema makes some of this information more critical.

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 fully describes the two parameters (limit and offset) with clear descriptions, so the description adds no additional parameter semantics. Baseline of 3 is appropriate given 100% schema coverage.

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 action ('List') and the resource ('VAST media'), and specifies the scope ('linear and non-linear'), which distinguishes it from sibling tools like vast_list_linear_media and vast_list_non_linear_media that focus on individual types.

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

Usage Guidelines3/5

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

The description implies that this tool covers both linear and non-linear media, offering a consolidated listing compared to the type-specific siblings. However, it does not explicitly state when to use this tool over alternatives, nor does it mention any exclusions or 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