Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

draft_list_rich_media_ad_items

List draft rich media ads from your AdButler account. Pagination options allow handling large result sets for efficient review and management.

Instructions

List all draft rich media ad items

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, the description carries the full burden of behavioral disclosure. It claims to 'List all' items but does not mention that the tool uses pagination via limit/offset, nor does it clarify whether 'all' means all across pages or just the current page. Read-only behavior is implied but not explicitly stated.

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, clear sentence with no unnecessary words. It is appropriately sized and front-loaded, conveying the core purpose immediately.

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 list tool with pagination parameters, the description is minimally adequate. However, it lacks context about the draft vs. non-draft distinction and how pagination interacts with 'all'. The presence of sibling tools like 'draft_list_ad_items' makes the missing clarification more significant, but the name and schema partially compensate.

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 provides 100% coverage with descriptions for 'limit' and 'offset', so the schema already documents these parameters. The description adds no additional meaning about how they affect the results, but the schema is sufficient. 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 'List all draft rich media ad items' uses a specific verb ('List'), a clear resource ('draft rich media ad items'), and distinguishes from sibling tools like 'draft_list_image_ad_items' and 'list_rich_media_ad_items' by explicitly targeting draft rich media items.

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. The description does not explain when to choose this over 'draft_list_ad_items' or the non-draft 'list_rich_media_ad_items', nor does it mention any prerequisites or context.

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