BayDeep — The e-commerce plugin for AI agents

search_products

LIVE AliExpress affiliate product search (100M+ item pool, ships to 200+ countries; prices in the target currency). Consumes platform quota — do not poll; prefer shelf_search for repeated lookups. Returns items with price, coupon, sales, rating, commission_rate and detail_url. Read-only. Requires a free API key.

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": {
      "q": "<q>"
    },
    "name": "search_products"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`page`	No
`sort`	No	SALE_PRICE_ASC \| SALE_PRICE_DESC \| AVERAGE_RATE_ASC \| AVERAGE_RATE_DESC \| ORDINAL_ASC \| ORDINAL_DESC
`ship_to`	No	ISO country code, default US
`currency`	No		USD
`language`	No		EN
`page_size`	No
`category_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares read-only behavior, an authentication prerequisite (free API key), and a quota cost with an anti-polling warning — exactly the operational traits an agent needs. It still omits rate-limit specifics and pagination/result-count behavior, keeping it short of a 5.

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?

A single dense paragraph that is front-loaded with the identity and capabilities, then the operational constraints, then the return fields. Every clause conveys distinct information and nothing is wasted.

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 an 8-parameter tool with no annotations and no output schema, the description covers the essentials: read-only nature, auth requirement, quota cost, currency semantics, and the shape of returned items. Gaps remain around pagination limits and total-result behavior, which matter for an 8-param paged search.

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 description coverage is only 25%, so only sort and ship_to are documented structurally; the description adds meaning for currency ('prices in the target currency') and indirectly for ship_to ('ships to 200+ countries'). It says nothing about q, page, page_size, language, or category_id, so half the parameters remain opaque.

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?

States a specific verb and resource ('LIVE AliExpress affiliate product search') plus concrete scope (100M+ item pool, 200+ countries, target-currency pricing). It also implicitly distinguishes itself from the shelf-oriented sibling by framing itself as the live/network lookup, so an agent can tell the two apart.

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?

Gives an explicit exclusion ('do not poll') and names the alternative for that case ('prefer shelf_search for repeated lookups'). It does not cover when to choose this over hot_products or product_detail, but the anti-polling guidance is the practically important routing decision here.

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

All BayDeep — The e-commerce plugin for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.