Search Amazon products by price and rating, or build curated shopping kits for any goal.
Build a curated shopping list for a goal or theme. Use for setups, gift lists, starter kits, or multi-category recommendations.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | best_match | |
| theme | Yes | ||
| budget | No | ||
| max_categories | No | ||
| products_per_category | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the high-level action (building a curated list) but does not explain how the curation works, whether it involves side effects, what output format to expect, or any constraints. The description is too thin to inform the agent about important behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, front-loaded with the main action and followed by usage examples. Every word contributes to understanding, and there is no redundancy. This is appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has five parameters, no output schema, and no annotations. The description provides only a high-level purpose and usage context but does not explain return values, parameter effects, or edge cases. The complexity of the tool warrants more detail than this description offers, making it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 0%, and the description provides no meaning for any of the five parameters (theme, sort, budget, max_categories, products_per_category). The parameter names are somewhat self-explanatory, but the description adds zero value over the schema, failing to explain how they interact or affect the result. This is a critical gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Build a curated shopping list for a goal or theme.' It specifies the resource (shopping list) and the verb (build), and distinguishes itself from the sibling search_products by focusing on multi-category curated outputs. The use cases (setups, gift lists, starter kits) further clarify purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists when to use the tool: 'Use for setups, gift lists, starter kits, or multi-category recommendations.' However, it does not name the sibling tool as an alternative or state when not to use it, so it falls short of a 5. The context is clear but lacks explicit exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Find individual products matching a query. Use for a specific item or category; supports price and rating filters.
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | best_match | |
| query | Yes | ||
| max_price | No | ||
| min_price | No | ||
| min_rating | No | ||
| max_results | No | ||
| amazon_domain | No | amazon.com | |
| exclude_sponsored | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool supports price and rating filters, but omits other behavioral traits such as the default sorting, sponsored filtering, or the Amazon domain parameter. The term 'Find' implies a read-only operation, but more detail on response behavior would improve transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the primary purpose, and contains no fluff. Every phrase earns its place, including the filter capabilities note.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 8 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return structure, pagination, or how filters interact, leaving substantial gaps for an agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It mentions price and rating filters, which roughly maps to min_price, max_price, and min_rating, but does not explain the purpose of sort, exclude_sponsored, amazon_domain, max_results, or query semantics. For 8 parameters, this is insufficient compensation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb ('Find individual products') and a resource ('matching a query'). It also distinguishes from the sibling tool by emphasizing 'individual products' versus 'build_product_kit', making the boundary explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises using it for 'a specific item or category', which provides clear context for appropriate use. It implicitly contrasts with the sibling tool 'build_product_kit' but does not explicitly mention when not to use it or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
build_product_kitsearch_productsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
AI shopping search: real, in-stock US and Amazon products with prices, ratings and buy links.
Product search for AI agents: Amazon + Shopify, cart-to-checkout buy path. Pay-per-call, no API key.
Real-time Amazon prices, product search, 90-day history, AI forecasts, and price drop alerts.
Product intel: Amazon, AliExpress, Shopify, TikTok Shop, ads and search interest.
Add one secure layer between your agents and this server.
build_product_kit is for creating curated multi-item lists, while search_products finds individual products. Their purposes are clearly different, and the descriptions reinforce the distinction, leaving no ambiguity.
Both tools use a consistent verb_noun pattern with snake_case, making the set predictable and easy to navigate. The naming style is uniform and intuitive.
With only two tools, the server feels thin for a shopping domain, but the pair covers both product search and curated list building, which are core use cases. This is borderline but not excessive.
The set covers product search and curated list creation, but lacks explicit product detail retrieval or list management. However, search likely returns sufficient details, and kits are generated on demand, so the gaps are minor.
