Skip to main content
Glama
adbutler

AdButler MCP Server

Official
by adbutler

list_advertisers

Retrieve a complete list of advertisers from your AdButler account with pagination controls to handle large result sets.

Instructions

List all advertisers in your AdButler account

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?

No annotations are provided, so the description carries the full burden. It only states 'List all advertisers' without disclosing pagination behavior, default limits, whether archived advertisers are included, or any other behavioral details. The description adds little beyond the tool name.

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 front-loads the action ('List all advertisers') followed by a minimal context phrase. There is no unnecessary information, and it is efficiently structured.

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?

This is a simple list tool with a straightforward return value implied. However, the description does not clarify whether archived advertisers are included, which is a notable gap given the existence of list_archived_advertisers. The schema covers pagination, so completeness is acceptable but not thorough.

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 covers both parameters (limit and offset) with descriptions, so schema coverage is 100%. The description does not add any information about these parameters, but the schema already provides adequate semantics, meeting the baseline for high coverage.

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 uses a specific verb and resource ('List all advertisers') and distinguishes from get_advertiser by implying multiple results. However, it does not explicitly state whether archived advertisers are included, which is ambiguous given the sibling tool list_archived_advertisers.

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 usage for listing advertisers but provides no explicit guidance on when to use this tool versus alternatives like list_archived_advertisers or get_advertiser. The context is clear but exclusions are not stated.

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