Skip to main content
Glama

Gloriads — Amazon Ads

Shopper journeys (Amazon Marketing Cloud)

get_shopper_journeys
Read-onlyIdempotent

Get what shoppers did before they bought on ONE marketplace, from Amazon Marketing Cloud, as the « Shopper journeys » page last computed it: the path to purchase across ad types (how many times more often shoppers who saw Sponsored Brands AND Sponsored Products bought), the days and ads before a purchase, the keywords that open journeys (sold nothing themselves but brought buyers through other ads: never negate them), and the share of new-to-brand customers in Sponsored Products (that Amazon's reports leave empty) with their 12-month value. Answers "should I cut Sponsored Brands?", "how long do my buyers take?" or "which keywords must I never negate?". status "not_open": Amazon Marketing Cloud was never opened for this marketplace; "computing": open, some analyses not computed yet (opening the page computes them). Results are confidential: for the advertiser and its agency.

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": "get_shopper_journeys"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoThe period: "30", "90" (default) or "365" days.
marketplace_idYesThe marketplace: an `id` from list_marketplaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation, so the description only needs to add context — and it does: results reflect the « Shopper journeys » page "as last computed", with "not_open" and "computing" statuses that require opening the page to compute analyses. It also flags the confidential audience (advertiser and its agency), a real behavioral constraint the annotations do not convey.

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

Conciseness3/5

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

The core purpose is packed into one very long sentence with multiple nested clauses and parentheticals, so the headline action competes with detail rather than being front-loaded. The status and confidentiality notes are separate and useful, but the first sentence would benefit from being split so an agent can scan the purpose first.

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

Completeness4/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 carries the burden of explaining return content, and it does so by listing the four analytical outputs and the brand-lens caveat that Amazon's own reports leave empty. Status semantics and confidentiality are also covered; only the parameter-level behavior (what the day-window changes) is left implicit.

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% and both parameters (days enum, marketplace_id from list_marketplaces) are documented in the schema, so baseline is 3. The description reinforces the single-marketplace scoping and implies a lookback window, but adds no syntax or selection guidance for `days` beyond what the schema already states.

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 names a specific verb and resource — what shoppers did before they bought on one marketplace, sourced from Amazon Marketing Cloud — and enumerates the concrete outputs (path to purchase across ad types, days/ads before purchase, journey-opening keywords, new-to-brand share and 12-month value). This is far more than a restatement of the name and clearly separates it from the report/listing siblings.

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 gives concrete triggering questions ("should I cut Sponsored Brands?", "how long do my buyers take?", "which keywords must I never negate?") and explains the status states that determine whether the data is usable, which tells the agent when this tool is the right call. It stops short of naming a sibling alternative for overlapping report needs, so it is clear context without explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources