list_ads
Retrieve ads within a specified ad group. Use parameters to paginate or sort results.
Instructions
List ads in an ad group.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ad_group_id | Yes | ||
| limit | No | ||
| after | No | ||
| before | No | ||
| order | No | desc |
Retrieve ads within a specified ad group. Use parameters to paginate or sort results.
List ads in an ad group.
| Name | Required | Description | Default |
|---|---|---|---|
| ad_group_id | Yes | ||
| limit | No | ||
| after | No | ||
| before | No | ||
| order | No | desc |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral context beyond 'list ads', such as sorting, filtering, or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no waste, but it lacks critical information, making it under-informative rather than appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 5 parameters, no output schema, and annotations present, the description is incomplete. It omits pagination, ordering, and limit behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description fails to explain any of the 5 parameters (ad_group_id, limit, after, before, order). No additional meaning provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (list) and resource (ads) with a specific scope (in an ad group). It effectively distinguishes from sibling tools like get_ad (single ad) and list_ad_groups.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., get_ad, get_ad_group). No mention of prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/trakkr-aisearch/openai-ads-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server