Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search Amazon

search_amazon
Read-only

Find Amazon product ASINs by keyword across selected marketplaces; returns up to 60 results, including sponsored listings, for product lookup.

Instructions

Search Amazon. Amazon search results (up to 60, sponsored included), to find the ASIN of a product. Free, limited to 30 searches per hour.

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": {
      "query": "<query>"
    },
    "name": "search_amazon"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords
marketplaceNoAmazon store, e.g. com for amazon.com Allowed values: com, co.uk, de, fr, it, es, ca, co.jp, com.br, com.mx, in. Default: "com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, open-world behavior, but the description adds real operational context: result cap of ~60, inclusion of sponsored results, free tier, and a 30-requests-per-hour rate limit. Passing over the return shape (fields per result) is the main remaining gap.

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?

Two tight sentences with the purpose and key constraints front-loaded and no filler. The leading 'Search Amazon.' restates the name, a minor redundancy, but the rest is dense with useful facts.

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 two-parameter, no-output-schema tool this is nearly complete: the agent knows what it searches, what comes back at a high level (up to 60 results, sponsored included), and the throttling limit. Only the per-result field structure and pagination behavior are unstated.

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?

Parameter description coverage is 100% and the marketplace enum values and default are fully documented in the schema, so the description adds nothing beyond it. Baseline 3 applies since the schema carries the parameter burden.

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 and resource ('Search Amazon') and adds intent ('to find the ASIN of a product'), which distinguishes a keyword lookup from the sibling get_product/check_product detail calls. It doesn't name an alternative explicitly, but the goal-driven framing makes the role clear.

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 stated goal ('to find the ASIN') implies when to reach for this tool, and indirectly signals the handoff to a product-detail tool once an ASIN is known. However, there is no explicit when-not or named alternative among the many siblings, so the agent must infer the boundary.

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