Gloriads — Amazon Ads

List campaigns

list_campaigns

Read-onlyIdempotent

List one marketplace's enabled and paused campaigns (Sponsored Products, Brands, Display): id, name, ad type, state, auto or manual targeting, daily budget (in the marketplace's currency) and whether Gloriads created or changed it. Read from the copy Gloriads keeps; meta.synced_at says when it was read from Amazon. Paginated: follow next_cursor while has_more is true.

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>"
    },
    "name": "list_campaigns"
  }
}

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.
`states`	No	Keep only these states: ENABLED, PAUSED. Archived ones are never listed.
`targeting`	No	Keep only automatic or manual campaigns.
`ad_products`	No	Keep only these ad types: SPONSORED_PRODUCTS, SPONSORED_BRANDS, SPONSORED_DISPLAY.
`marketplace_id`	Yes	The marketplace: an `id` from list_marketplaces.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (which already mark it read-only, idempotent and closed-world), it discloses the crucial trait that results come from Gloriads' cached copy and that `meta.synced_at` reveals staleness, plus the has_more/next_cursor loop and that archived campaigns are excluded.

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?

Three dense sentences lead with scope, then data provenance, then pagination. The long parenthetical field enumeration is heavy but each clause carries useful information; little is wasted.

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 listing the returned fields and their units (daily budget in marketplace currency, creation/change provenance), and it fully explains pagination and data freshness — everything needed to call and interpret it.

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 all six parameters, including the states/targeting/ad_products filters and cursor semantics, are already documented. The description only reinforces paging behavior and currency context without adding parameter-level detail.

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?

States a specific verb and resource ('List ... campaigns') scoped to one marketplace, names the three ad types, enumerates returned fields, and is clearly distinct from siblings like list_ad_groups and list_ads.

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?

Clearly frames the context: one marketplace at a time, only ENABLED/PAUSED (archived never listed), and instructs how to page through results. It does not name specific alternatives, but the sibling set is other resources rather than overlapping list tools, so the guidance is adequate.

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?