mercadolivre-mcp

Descrição do anúncio

get_item_description

Retrieve the description text of a Mercado Livre listing to check condition or battery details mentioned in used items; excludes price.

Instructions

Texto da descrição de um anúncio (vale para terceiros; útil para conferir estado/bateria mencionados em usados). Sem preço.

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_id": "<item_id>"
    },
    "name": "get_item_description"
  }
}

Input Schema

Name	Required	Description	Default
`item_id`	Yes	id do anúncio

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 at all, the description carries the full behavioral burden; it does disclose the output boundary ('sem preço') and that third-party items are covered, which is real added context. It says nothing about permissions, error behavior when no description exists, or return shape, which is a notable gap for an annotation-free tool.

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?

Extremely short and front-loaded: the resource is stated first, then scope, then use case, then the output exclusion. The parenthetical style is slightly telegraphic but nothing is wasted.

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 no output schema and no annotations, the essentials are present, but the description never says what happens if a listing has no description text or whether the result is a bare string. Adequate rather than complete.

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 100% and the single parameter 'item_id' is documented as 'id do anúncio'. The description adds no further meaning about the identifier (e.g., whether it accepts the same id form as get_item), so this sits at the schema-backed baseline.

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 names a specific resource — the description text of a listing ('Texto da descrição de um anúncio') — so an agent knows exactly which field it returns, as opposed to get_item or get_product which return broader records. It stops short of explicitly naming those siblings as alternatives, so differentiation is only implicit.

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?

'útil para conferir estado/bateria mencionados em usados' gives a concrete use case, and 'vale para terceiros' signals it works on other sellers' listings, not just own items. 'Sem preço' implicitly delimits it against price-bearing tools, but no sibling is named and no when-not guidance is stated outright.

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

Deploy Server