Skip to main content
Glama

Traject Ecommerce

by io.github.pipeworx-io

Amazon Search

amazon_search
Read-onlyIdempotent

Search Amazon products by keyword — returns position, title, ASIN, price, rating, and ratings total. Uses your Rainforest API key. Example: amazon_search({ search_term: "wireless earbuds", amazon_domain: "amazon.com", _apiKey: "your-rainforest-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesYour Rainforest API key (get one at trajectdata.com)
search_termYesSearch query, e.g. "wireless earbuds"
amazon_domainNoAmazon marketplace domain (default "amazon.com")

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that it uses a Rainforest API key, which is crucial for usage. No contradictions.

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?

Two concise sentences plus an example. Every word serves a purpose, with no redundancy. Front-loaded with the key action and output.

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 and comprehensive annotations, the description covers the core functionality. It lists return fields and includes an example. Could optionally mention result limits, but not critical for this use case.

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?

Schema coverage is 100% with descriptions for each parameter. The description reinforces this with an example demonstrating all parameters in context, adding practical usage information beyond the schema.

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?

The description clearly states 'Search Amazon products by keyword' with specific verb and resource. It lists returned fields (position, title, ASIN, etc.), distinguishing it from sibling tools like amazon_product and amazon_reviews.

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?

The example shows how to call the tool. While it doesn't explicitly state when not to use it, the context of the name and siblings implies its scope. Clear usage guidance is provided via the example and API key mention.

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