Rally MCP Server

search_products

Search products on Mercado Libre and Shopee with affiliate commission estimates. Get product details including title, price, image, commission rate, and estimated earnings.

Instructions

Search products on Mercado Libre or Shopee with affiliate commission estimates. Returns product list with title, price, image, commission rate, and estimated earnings.

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

Input Schema

Name	Required	Description	Default
`marketplace`	Yes	Target marketplace
`query`	Yes	Search query (product name, category, keyword)
`category`	No	Category ID (e.g., MLB1051 for phones)
`sort`	No		relevance
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Discloses that the tool is a search operation that returns a list of products with specific fields, including commission estimates. No annotations provided, but description accurately implies read-only behavior. Does not mention pagination or rate limits.

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 that is front-loaded with the core action and efficiently packs all key information: target marketplaces, commission estimates, and returned fields. No wasted words.

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 no output schema and no annotations, the description explains the output format (list with specific fields) and the main input parameters. However, lacks details on pagination, error handling, or optional parameter behavior, which are partially covered by the input schema.

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?

Adds meaning beyond schema by describing return fields (title, price, image, commission rate, estimated earnings) and implicitly linking 'marketplace' to the two enums. Compensates for 60% schema description coverage by providing output context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool searches products on Mercado Libre or Shopee and returns commission estimates. Identifies specific fields in results. However, does not distinguish itself from sibling 'trending_products' which may also search products.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'trending_products', 'analyze_product', or 'commission_calculator'. Lacks explicit when-to-use or when-not-to-use instructions.

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

Deploy Server