mercadolivre-mcp

Termos em alta

get_trends

Retrieve frequently searched terms within a specific Mercado Livre category to reveal current consumer interest and support product research.

Instructions

Termos mais buscados numa categoria (descoberta pública do que está quente).

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": {
      "category_id": "<category_id>"
    },
    "name": "get_trends"
  }
}

Input Schema

Name	Required	Description	Default
`category_id`	Yes	id da categoria (ex. MLB1051)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does hint that the data is public ("descoberta pública"), which weakly suggests no special auth, but it says nothing about result shape, how many terms are returned, ranking method, time window for "hot", or caching/rate behavior.

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?

A single compact sentence with the resource front-loaded and the parenthetical serving as immediate context. No filler or repetition, though the terseness leaves room for one more clarifying clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full schema coverage and no output schema, the essential calling information is present. However, an agent cannot tell what the response looks like (a ranked list of terms?) or how "trending" is scoped in time, which the description should have supplied since no output schema exists.

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?

The single parameter is fully documented in the schema (100% coverage, including the example format MLB1051). The phrase "numa categoria" merely restates that filtering dimension without adding format or validity details beyond what the schema already provides, so the baseline of 3 applies.

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?

The description states a specific resource (most searched terms) scoped to a category, and the parenthetical clarifies it is a public trending-discovery lookup. This is clearly distinguishable from sibling tools like search_products or get_item, though it never names an alternative to reinforce that distinction.

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

Usage Guidelines3/5

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

Usage is only implied through the parenthetical "descoberta pública do que está quente", which signals a discovery/trending scenario. There is no explicit statement of when to prefer this over search_products or browse_category, and no prerequisites or exclusions are given.

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

Deploy Server