Skip to main content
Glama

intentlink

by io.github.whalefuntech

search_products

Search affiliate shopping products and get ranked recommendations.

Only query is required — a natural-language description of what the shopper wants (e.g. "a warm waterproof jacket for winter hiking"). Add fields to narrow results:

  • keywords: exact product terms. Use a SPECIFIC product type ("women running shoes", "stainless steel knife set"), not a bare generic noun ("shoes", "knife") — a generic keyword can surface the wrong audience. Audience/occasion go in query.

  • commerce_l2s: category ids to restrict to (read the commerce://categories resource for valid values — that taxonomy is for shopping only).

  • max_price / min_price: price band (USD). platforms: ["amazon"|"walmart"] (empty=all).

  • intent: ranking preset — "cheapest" | "best_discount" | "top_rated" | "best_value".

  • require_commission: only return products that pay a commission (default: server setting, normally on). Pass false to include zero/unknown-commission products.

  • limit: max results (default 10).

agent_id is REQUIRED: your registered, active agent id. It is the attribution key and the access key — a missing/blank or unregistered agent_id is rejected (no anonymous use).

Returns {count, products:[{offer_id,title,brand,price,rating,...,buy_url,product_url}]}. Each product's buy_url is ALREADY the trackable affiliate buy link — hand it to the shopper directly. (product_url is the plain product page.) There is no separate resolve/click step.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
intentNo
agent_idYes
keywordsNo
max_priceNo
min_priceNo
platformsNo
commerce_l2sNo
require_commissionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses required agent_id (attribution key), that buy_url is already trackable, default for require_commission, and return structure. 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.

Conciseness4/5

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

Well-structured with clear summary and bullet points. Slightly long but each sentence adds value; could be slightly more concise without losing clarity.

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?

Comprehensive coverage of all 10 parameters, required fields, default behaviors, and output structure (with output schema present). No gaps for a search tool with many parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description compensates fully. Every parameter (query, keywords, commerce_l2s, price bounds, platforms, intent, require_commission, limit, agent_id) is explained with usage tips, constraints, and defaults.

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 explicitly states the tool searches affiliate shopping products and returns ranked recommendations. It distinguishes from siblings (events, travel) by specifying 'affiliate shopping products'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides detailed guidance: distinguishes between query (natural language) and keywords (exact product terms), explains constraints on keywords, references the commerce categories resource, explains commission and agent_id requirements, and describes default behaviors.

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

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

A4.6/5.0
Disambiguation5/5

Each tool targets a distinct domain: events, products, and travel. Their purposes are clearly differentiated, with no overlap or ambiguity.

Naming Consistency5/5

All three tools follow a consistent 'search_<domain>' pattern (search_events, search_products, search_travel), making it easy to infer functionality from the name.

Tool Count4/5

Three tools is a small set, but it covers the primary domains (events, shopping, travel) that the server is designed for. It is well-scoped and not overly sparse.

Completeness4/5

The server provides comprehensive search for three major categories. While additional categories could be added, the current set handles common use cases. The descriptions include filtering, pagination, and direct buy links, leaving no obvious dead ends.

Resources