Skip to main content
Glama
Sign In
Amazon Selling Central MCP

Amazon Selling Central MCP

by KuudoAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Sellers_getMarketplaceParticipations

Get the marketplaces a seller is enrolled in and their participation details.

Instructions

Catalog entry. Runs in your Kuudo deployment, not here. Returns a list of marketplaces where the seller can list items and information about the seller's participation in those marketplaces.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It indicates a read-only, list-returning operation and notes the deployment quirk, but it does not mention authentication, rate limits, pagination, or any side effects. This is adequate for a simple zero-parameter read but not rich.

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?

The description is short and the key return semantics appear in the second sentence. The opening fragment 'Catalog entry' is vaguely redundant and 'Runs in your Kuudo deployment, not here' is awkwardly phrased, but there is no padding.

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?

For a zero-parameter read operation without an output schema, the description gives enough high-level return information to invoke correctly: a list of marketplaces and participation details. It omits response structure details, but the simplicity of the tool makes the definition sufficient.

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?

There are zero parameters, so the baseline is 4. The description adds no parameter-specific detail, but none is needed since the schema is empty and fully covers this aspect.

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 states a specific verb and resource: it returns a list of marketplaces where the seller can list items and information about the seller's participation. This clearly identifies the tool's purpose and distinguishes it from account-level Sellers tools like Sellers_getAccount.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or alternative guidance, but the sentence 'Runs in your Kuudo deployment, not here' provides a useful deployment constraint. The unique purpose among siblings makes the usage context reasonably implied, though the description does not state exclusions or conditions.

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

Deploy Server

Other Tools