Skip to main content
Glama
Sign In
Amazon Selling Central MCP

Amazon Selling Central MCP

by KuudoAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Replenishment20221107_listOffers

Retrieve replenishment program offer details for a selling partner, providing visibility into available offers for restocking decisions.

Instructions

Catalog entry. Runs in your Kuudo deployment, not here. Returns the details of a selling partner's replenishment program offers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-like behavior with 'Returns' and adds a deployment caveat, but it does not disclose output behavior, pagination, authorization needs, or what 'not here' actually means for invocation.

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 description is short, but the first sentence 'Catalog entry.' is unhelpful filler and does not front-load the core function. The second sentence is concise and informative, but not every sentence earns its place.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description should provide more behavioral and return-value context. It does not describe the response shape, list vs. single result, pagination, or the practical meaning of 'Runs in your Kuudo deployment, not here.'

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?

The tool has zero declared parameters, so the baseline is 4. The empty schema and 100% schema description coverage mean there are no parameter semantics for the description to explain.

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?

The description says the tool 'Returns the details of a selling partner's replenishment program offers,' which names a specific verb, resource, and scope. It can be distinguished from sibling metric-returning tools, though the opening 'Catalog entry' is unexplained and slightly muddies the purpose.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool versus the similarly named Replenishment_listOffers or other Replenishment20221107 siblings. The deployment note 'Runs in your Kuudo deployment, not here' hints at a constraint but does not help an agent choose among alternatives.

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