Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Amazon Seller Connector

amazon_seller_connector
Read-onlyIdempotent

Amazon Seller Central data: orders, inventory, sales metrics, and seller account performance. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYeslist_amazon_orders: List orders from the seller's Amazon store with optional date and status filters. Returns order summaries with order ID, | get_amazon_order: Get full details for a single Amazon order by order ID: shipping address, buyer info, payment method, fulfillment channe | get_amazon_order_items: Get the line items (products) for a specific Amazon order: ASIN, seller SKU, title, quantity ordered/shipped, item price | get_amazon_sales_metrics: Get order metrics (revenue and units) for a time interval with a chosen granularity. Returns unit count, order count, an | list_amazon_inventory: Get FBA inventory summaries: ASIN, SKU, product name, fulfillable quantity, inbound, and reserved stock. Use when user a | list_amazon_listings: List the seller's product listings: SKU, ASIN, product type, item name, and listing status. Use when user asks 'what pro | get_amazon_catalog_item: Get catalog details for an Amazon product by ASIN: title, brand, manufacturer, product type, color, size, and main image | get_amazon_finances: List Amazon financial event groups (settlement periods): total amounts, fund transfer status, settlement dates, and acco | get_amazon_marketplace_participations: List all Amazon marketplaces the seller participates in, including marketplace IDs, country codes, and participation sta
paramsNoAction-specific parameters. list_amazon_orders: {created_after?: string, created_before?: string, order_statuses?: array, fulfillment_channels?: array, max_results?: integer, next_token?: string} | get_amazon_order: {order_id: string} | get_amazon_order_items: {order_id: string} | get_amazon_sales_metrics: {interval: string, granularity?: string} | list_amazon_inventory: {skus?: array, start_date_time?: string, max_results?: integer, next_token?: string} | list_amazon_listings: {max_results?: integer, page_token?: string} | get_amazon_catalog_item: {asin: string} | get_amazon_finances: {started_after?: string, started_before?: string, max_results?: integer, next_token?: string} | get_amazon_marketplace_participations: none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"get_orders: List Amazon Seller orders with status and financial details | get_inventory: Get Amazon Seller inventory levels and FBA stock"New value: +"list_amazon_orders: List orders from the seller's Amazon store with optional date and status filters. Returns order summaries with order ID, | get_amazon_order: Get full details for a single Amazon order by order ID: shipping address, buyer info, payment method, fulfillment channe | get_amazon_order_items: Get the line items (products) for a specific Amazon order: ASIN, seller SKU, title, quantity ordered/shipped, item price | get_amazon_sales_metrics: Get order metrics (revenue and units) for a time interval with a chosen granularity. Returns unit count, order count, an | list_amazon_inventory: Get FBA inventory summaries: ASIN, SKU, product name, fulfillable quantity, inbound, and reserved stock. Use when user a | list_amazon_listings: List the seller's product listings: SKU, ASIN, product type, item name, and listing status. Use when user asks 'what pro | get_amazon_catalog_item: Get catalog details for an Amazon product by ASIN: title, brand, manufacturer, product type, color, size, and main image | get_amazon_finances: List Amazon financial event groups (settlement periods): total amounts, fund transfer status, settlement dates, and acco | get_amazon_marketplace_participations: List all Amazon marketplaces the seller participates in, including marketplace IDs, country codes, and participation sta"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "get_orders",
-  "get_inventory"
-]New value: +[
+  "list_amazon_orders",
+  "get_amazon_order",
+  "get_amazon_order_items",
+  "get_amazon_sales_metrics",
+  "list_amazon_inventory",
+  "list_amazon_listings",
+  "get_amazon_catalog_item",
+  "get_amazon_finances",
+  "get_amazon_marketplace_participations"
+]
    • changedInput schema / properties / params / description
      Previous value: -"Action-specific parameters. get_orders: {limit?: integer, created_after?: string, order_statuses?: array} | get_inventory: {limit?: integer}"New value: +"Action-specific parameters. list_amazon_orders: {created_after?: string, created_before?: string, order_statuses?: array, fulfillment_channels?: array, max_results?: integer, next_token?: string} | get_amazon_order: {order_id: string} | get_amazon_order_items: {order_id: string} | get_amazon_sales_metrics: {interval: string, granularity?: string} | list_amazon_inventory: {skus?: array, start_date_time?: string, max_results?: integer, next_token?: string} | list_amazon_listings: {max_results?: integer, page_token?: string} | get_amazon_catalog_item: {asin: string} | get_amazon_finances: {started_after?: string, started_before?: string, max_results?: integer, next_token?: string} | get_amazon_marketplace_participations: none"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description is fully consistent with that read-only profile. It adds genuinely non-obvious behavior: a 15-minute provenance-token validity window usable across replicas, mapping of values to source_path, and the rule that unverified values are labeled unverified_model_data. It says nothing about rate limits, pagination limits, or permissions, so it stops short of 5.

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?

Purpose is correctly front-loaded, but the body is a long block in which the majority of sentences describe chart_render and attribution behavior rather than this connector. The provenance and accuracy-contract content is relevant yet disproportionately verbose and reads like shared boilerplate.

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 9 actions, nested params, no output schema, and annotations already carrying the safety profile, what remains genuinely useful is the data-integrity and verification contract, which the description supplies. Gaps are minor: nothing tells the agent about the connector's own limits (pagination, throttling, auth scope) beyond what annotations state.

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?

Schema description coverage is 100%, and the enum plus params object fully document all nine actions and their per-action arguments, so the baseline is 3. The description adds no parameter-level detail (formats, defaults, constraints) beyond what the schema already provides.

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 opening sentence names the resource and its content domains precisely ('Amazon Seller Central data: orders, inventory, sales metrics, and seller account performance'), so an agent knows this is the Amazon seller data connector. It does not state a verb or explicitly differentiate from siblings like ebay_connector or shopify_dashboard, but the domain is unambiguous.

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?

The description gives extensive guidance on how to consume results (when to call chart_render, when to pass provenance_token, attribution footer handling) but says nothing about when to select this connector over alternatives or what preconditions the seller account must satisfy. Tool-selection guidance is only implied by the data domain.

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

All CorpusIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources