mercadolivre-mcp

Preços em lote

get_items

Retrieve prices and details for up to 20 Mercado Livre listings from your own account in a single request.

Instructions

Preço/detalhe de até 20 anúncios da própria conta numa chamada.

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": {
      "item_ids": "<item_ids>"
    },
    "name": "get_items"
  }
}

Input Schema

Name	Required	Description	Default
`item_ids`	Yes	ids dos anúncios

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does add two useful facts: the call is restricted to the caller's own account (an auth/scope constraint) and is capped at 20 items, but it says nothing about what happens with invalid or missing IDs, whether results are ordered, or whether the response is a partial success.

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 short sentence with no wasted words, and the scope and batch limit are front-loaded. The slash-joined 'Preço/detalhe' is slightly loose but does not cost much.

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 lookup tool this is close to adequate, and the own-account restriction is valuable. Since there is no output schema, the description could have said what each returned entry contains (price fields, detail fields, error entries), leaving a real gap for an agent deciding whether one call suffices.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents item_ids and its 1-20 bounds. The description's 'até 20' merely restates maxItems and adds no format or validation detail beyond the schema; baseline 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?

States a specific resource (price/detail of listings) with a scope qualifier ('da própria conta') and a batch cap (up to 20) in one call, which distinguishes it broadly from search_products or browse_category. It does not, however, differentiate itself from the very close siblings get_item and get_own_items, and 'Preço/detalhe' leaves ambiguous whether price, detail, or both are returned.

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?

Batch usage ('numa chamada', up to 20) implies the intended case: fetching many own listings at once rather than one. There is no explicit statement of when to prefer get_item for a single listing or get_own_items for a full listing, and no exclusions or prerequisites are named.

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

Deploy Server