Skip to main content
Glama
Imsamiullah09

amazon-ads-mcp

List Sponsored Products ad groups

sp_list_ad_groups
Read-only

Retrieve Sponsored Products ad groups filtered by campaign or state. Supports pagination with nextToken for large result sets.

Instructions

List Sponsored Products ad groups (v3), optionally filtered to specific campaigns. Paginate with nextToken.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileIdNoAmazon Ads profile id (Amazon-Advertising-API-Scope). Omit to use the AMAZON_ADS_PROFILE_ID default. Discover ids with get_profiles.
stateFilterNoFilter by entity state. Omit for all states.
campaignIdsNoRestrict to these campaign ids.
maxResultsNoPage size (Amazon max varies by endpoint; <=1000).
nextTokenNoOpaque pagination token from a previous response.
Behavior4/5

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

The description indicates a read-only 'List' operation, aligning with the 'readOnlyHint' annotation. It adds context about pagination via nextToken. No contradictions, and the description complements the annotations by confirming the safety profile.

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?

Two sentences: one for purpose and version, one for optional filtering and pagination. Every sentence is essential, no unnecessary words. Highly efficient.

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?

Given no output schema, the description is adequate but not comprehensive: it omits mention of state filtering and profileId handling. It covers the core functionality but could be more complete.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing optional filtering and pagination, but the schema descriptions already provide detailed param info, so the added meaning is marginal.

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 'List Sponsored Products ad groups (v3)', providing a specific verb ('List'), resource ('Sponsored Products ad groups'), and version. It distinguishes from siblings like 'sb_list_ad_groups' and 'sd_list_ad_groups' by the product type.

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 mentions that the tool can be optionally filtered to specific campaigns and pagination with nextToken, but does not provide explicit guidance on when to use it over sibling tools (e.g., sp_list_campaigns, sb_list_ad_groups). No when-not-to-use or alternative tool mentions.

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/Imsamiullah09/amazon-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server