Skip to main content
Glama

Pet Welcome Box – hand-picked gift ideas

List Amazon marketplaces

list_marketplaces
Read-only

List supported Amazon storefronts (id, domain, defaultLocale, currency, catalogCount, trackingTag). amazon.com (US) and amazon.se (Sweden, default) have hand-picked catalogs. Pass marketplace (e.g. amazon.com) + locale (e.g. en-US) on shopping tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_marketplaces"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds real value beyond that: the exact returned fields, that only amazon.com and amazon.se have hand-picked catalogs, and that amazon.se is the default — domain facts an agent cannot get from annotations.

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 tight sentences with the resource and field list front-loaded, then the catalog note, then the handoff instruction. The parenthetical field enumeration is dense but earns its place since there is no output schema; a minor trim is possible but nothing is wasted.

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 correctly carries the return-shape burden by listing fields, and it flags the catalog/default nuances. It does not mention ordering, whether unsupported/disabled marketplaces appear, or total result size, which are minor residual gaps for a zero-param lister.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the 4 baseline applies. The description goes slightly further by explaining how the returned values feed parameters on other tools (marketplace + locale), but there are no local parameters to disambiguate.

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+resource ('List supported Amazon storefronts') and enumerates exactly what each entry contains (id, domain, defaultLocale, currency, catalogCount, trackingTag). This makes it immediately distinguishable from the mutation/search siblings without opening any schema.

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?

Provides clear downstream guidance: 'Pass marketplace (e.g. amazon.com) + locale (e.g. en-US) on shopping tools,' which implicitly tells the agent this is a discovery call to make before search/resolve_product. It stops short of an explicit 'call this first' or any exclusions, so it is clear context rather than a full when/when-not rule.

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