Gloriads — Amazon Ads

A campaign's ads

list_ads

Read-onlyIdempotent

List ONE campaign's ads, read live from Amazon: the product each advertises (ASIN or SKU; a Sponsored Brands ad lists its ASINs), its ad group and state. No figures. Answers "which products does this campaign advertise?". Paginated like list_targets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "marketplace_id": "<marketplace_id>",
      "campaign_id": "<campaign_id>"
    },
    "name": "list_ads"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Items per page, 1 to 1000. Defaults to 100.
`cursor`	No	The `next_cursor` of the previous page, to read the next one. Treat it as opaque.
`ad_group_id`	No	Keep only this ad group of the campaign: an `id` from list_ad_groups.
`campaign_id`	Yes	The campaign: an `id` from list_campaigns.
`marketplace_id`	Yes	The marketplace: an `id` from list_marketplaces.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that data is read live from Amazon (freshness, possible latency) and that no performance figures are returned, but it leaves pagination behavior delegated to a sibling reference rather than stating it here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Scope and the key constraint ('No figures') are front-loaded, and each sentence carries information the agent needs. The closing 'Paginated like list_targets' is slightly oblique because it requires opening another tool's definition to interpret, which keeps it just under top marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the fields returned per ad (product identifier, ad group, state) and explicitly ruling out metrics. Combined with the annotated read-only profile and the fully described parameter schema, nothing essential for a correct call is missing.

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 description coverage is 100%, so every parameter (marketplace_id, campaign_id, ad_group_id, limit, cursor) is already documented with provenance pointers to list_campaigns, list_ad_groups and list_marketplaces. The description only adds that results are paginated and comparable to list_targets, which is marginal beyond the schema; baseline 3 applies.

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 gives a specific verb and resource ('List ONE campaign's ads'), states the source ('read live from Amazon'), and enumerates the returned fields (advertised ASIN or SKU, ad group, state). The 'ONE campaign' emphasis and 'No figures' clause clearly separate it from metrics/report siblings like get_products_report.

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

Usage Guidelines4/5

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

It supplies a concrete triggering question ('which products does this campaign advertise?') and an exclusion ('No figures'), which implies metrics questions should go elsewhere. It stops short of naming the specific sibling to use for figures or for cross-campaign ad listing, so routing is clear but not fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Gloriads — Amazon Ads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?