Skip to main content
Glama

Nova Amazon MCP Server

list_accounts

Read-only

List the seller's Amazon accounts you can query (id, name, region, channel, the marketplaces each sells on with their country code and domain, and the workspace(s) each belongs to). channel is the Amazon programme the account sells through: 'SELLER' = Seller Central (3P, the seller sells to Amazon's customers), 'VENDOR' = Vendor Central (1P, Amazon buys the products from the vendor and resells them). query_metrics, find_movers and explain_movement read Seller Central unless you pass channels=['VENDOR'], or channels=['SELLER','VENDOR'] for All channels; never add 3P and 1P figures yourself. Accounts can span several workspaces (e.g. an agency's separate clients) — use the workspaces field to tell them apart, and the accounts filter of the other tools to focus on one account or client.

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_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and closed-world, so safety is covered. The description adds genuinely useful behavioral context beyond that: the returned field set, the SELLER/3P vs VENDOR/1P taxonomy, the warning never to add 3P and 1P figures together, and the fact that one account can span multiple workspaces.

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?

Content is front-loaded: the field list and channel semantics come first, cross-tool filtering rules last. It is dense but nearly every clause carries information an agent needs; the parenthetical field enumeration is long yet functional since no output schema exists.

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 carries the burden of describing return values and does so explicitly (id, name, region, channel, marketplaces, workspaces). For a one-optional-parameter read tool, nothing an agent needs in order to call it or interpret the result 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?

There is a single parameter (`reason`) and schema description coverage is 100%, with the schema itself spelling out the English-only, one-sentence requirement. The description adds no meaning on top of that, so the high-coverage baseline of 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?

Opens with a specific verb+resource ('List the seller's Amazon accounts you can query') and enumerates exactly what each entry contains (id, name, region, channel, marketplaces with country code and domain, workspaces). This clearly separates it from data-returning siblings like query_metrics or explain_movement.

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?

Explains downstream routing precisely: other tools read Seller Central unless channels=['VENDOR'] or ['SELLER','VENDOR'] is passed, and points to the `workspaces` field and the `accounts` filter to narrow scope. It stops short of an explicit 'call this first to discover account ids', leaving the discovery-first sequencing implied rather than stated.

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.