Skip to main content
Glama

Traject Ecommerce

by io.github.pipeworx-io

Amazon Reviews

amazon_reviews
Read-onlyIdempotent

Get customer reviews for an Amazon product by ASIN — title, body, rating, date, verified-purchase flag, and helpful votes. Uses your Rainforest API key. Example: amazon_reviews({ asin: "B08N5WRWNW", amazon_domain: "amazon.com", _apiKey: "your-rainforest-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asinYesAmazon Standard Identification Number, e.g. "B08N5WRWNW"
_apiKeyYesYour Rainforest API key (get one at trajectdata.com)
amazon_domainNoAmazon marketplace domain (default "amazon.com")

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds the authentication requirement (API key) and lists return fields, but does not disclose pagination behavior or rate limits. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with a clear list of return fields and an example. No fluff. Front-loaded with the action and resource.

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?

Given the tool's simplicity (3 parameters, no output schema but good annotations), the description covers purpose, return fields, and auth. It lacks details on pagination or result count, but this is acceptable for a straightforward read-only tool.

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 covers all 3 parameters with descriptions (100% coverage). Description adds an example call with sample values, which provides additional context but does not significantly extend beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'Get customer reviews for an Amazon product by ASIN' and lists specific fields returned. Differentiates from siblings like amazon_product (product details) and amazon_search (search results) by focusing on reviews only.

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?

Provides usage context by mentioning the Rainforest API key requirement and an example call, but does not explicitly state when to use this tool versus sibling tools like walmart_reviews or amazon_product.

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

All Traject Ecommerce toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have distinct purposes, e.g., Amazon and Walmart tools are platform-specific. A few overlapping tools like ask_pipeworx, ask_pipeworx_grounded, and deep_research are differentiated by clear usage guidance, so an agent can disambiguate with reasonable effort.

Naming Consistency3/5

Tool names mix verbs and nouns with varying styles (e.g., ai_visibility_check, compare_entities, scan_competitor_ai_presence). There is no uniform pattern like verb_noun; some are descriptive phrases. The inconsistency is noticeable but not chaotic.

Tool Count2/5

36 tools is too many for a server named 'Traject Ecommerce', as many tools cover unrelated domains (Polymarket, npm packages, SEC filings). The scope is excessively broad, making the server feel like a general-purpose plugin rather than a focused ecommerce toolset.

Completeness2/5

For an ecommerce-focused server, it only covers Amazon and Walmart product/search/reviews, missing major platforms and backend operations. The broader tool set is detailed but not ecommerce-specific, leaving obvious gaps for the intended purpose.

Resources