Skip to main content
Glama

Amazon Seller MCP Server — AgentXray

List connected seller accounts

list_my_accounts
Read-onlyIdempotent

List the Amazon seller accounts connected to this workspace, with the marketplaces each one covers. An agency has one per client; a single seller has one. Every marketplace-scoped tool takes an 'account' argument naming which of them to answer about, and refuses rather than guessing when several could apply.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 cover read-only, idempotent, non-destructive, closed-world traits. The description adds genuine context beyond them: cardinality (one account per client for an agency, one for a single seller) and the downstream refusal behavior when an account is ambiguous.

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

Conciseness5/5

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

Three tightly packed sentences, front-loaded with the primary action; each subsequent sentence adds distinct information (contents, cardinality, downstream usage) with no filler.

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?

No output schema exists, so the description must convey the return shape — and it does, describing accounts together with the marketplaces each covers. Adequate for a zero-parameter read tool.

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 baseline is 4. The description usefully explains the 'account' argument convention shared by sibling tools, which helps the agent understand the broader call pattern even though this tool takes no arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("List") and resource ("Amazon seller accounts connected to this workspace") plus what each entry contains (marketplaces covered). Clear, but it does not explicitly contrast with the sibling list_my_marketplaces, so sibling differentiation is left to inference.

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 the tool's role as the source of the 'account' argument consumed by every marketplace-scoped tool, and notes the refuse-rather-than-guess behavior. Clear context for when to use it, though no explicit exclusion versus list_my_marketplaces.

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