Skip to main content
Glama
Sign In

HasData

by com.hasdata
OverviewDiscussionsAdmin

amazon_seller: GET /

hasdata_amazon_seller_getSellerDetails
Read-only

Get Amazon Seller Details

Fetches the public storefront profile for an Amazon seller by sellerId on the chosen domain/language. Returns business name, seller logo, About-this-seller text, overall feedback rating and lifetime/12-month/90-day/30-day rating breakdown, feedback count, business address and contact details, and customer service info. Use for seller due-diligence and vetting, counterfeit/brand-protection workflows, MAP-violation investigations, building seller leaderboards, and enriching marketplace seller directories.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sellerId": "<sellerId>"
    },
    "name": "hasdata_amazon_seller_getSellerDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoAmazon domain to use. Default is www.amazon.com.
languageNoOptional Amazon language code. Supported values depend on the selected domain.
sellerIdYesThe unique Amazon seller ID.

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 openWorldHint=true, so the safety profile is covered structurally. The description adds useful behavioral context by characterizing the profile as 'public' and enumerating the returned fields (ratings breakdown, feedback counts, address, contact, customer service), though it omits auth requirements, rate limits, and pagination.

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?

Front-loads the verb and resource, then supplies return detail and use cases in a logical order with no filler. The opening line duplicates the title, and the return-field inventory plus five-item use-case list push length, but each element is informative.

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 enumerated return fields replace what an output schema would normally provide, and the annotations cover the safety profile. Three parameters at 100% coverage leaves nothing material about calling the tool unexplained.

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 both enums (domain, language) are self-documented with defaults and constraints. The description only restates sellerId and the domain/language selection, adding no format, range, or dependency detail beyond the schema, so the baseline 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?

States a specific verb ('Fetches') and resource ('public storefront profile for an Amazon seller') and identifies the key ('by sellerId') plus scope ('chosen domain/language'). This is clearly distinguishable from siblings like getProductDetails, getProductReviews, and getSellerProducts, so an agent can route without opening schemas.

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?

Gives concrete when-to-use scenarios (due-diligence/vetting, brand protection, MAP-violation investigations, leaderboards, directory enrichment), which is strong context. However, it never states when not to use it or names the natural alternative (getSellerProducts for listing a seller's catalog), leaving that inference to the agent.

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

All HasData 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