Skip to main content
Glama
Sign In
mercadolivre-mcp

mercadolivre-mcp

by romualdoag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Preço do anúncio

get_item

Retrieve price and details for your own Mercado Livre listing by item ID; the API rejects third-party ads with this token.

Instructions

Preço e detalhe de um anúncio da PRÓPRIA conta (a API nega anúncios de terceiros com este token).

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesid do anúncio (ex. MLB4746731943)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden, and it does disclose one genuinely non-obvious behavior: the token scope causes the API to reject listings belonging to other accounts. Beyond that scope constraint it says nothing about rate limits, error behavior, or what 'detalhe' concretely includes, which is thin 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?

A single front-loaded sentence with zero padding, and the important constraint sits in parentheses right where it is needed. It is efficient, though its brevity contributes to the missing sibling differentiation.

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 description is adequate but leaves real ambiguity: it is unclear whether 'detalhe' overlaps with get_item_description or get_item_questions, and there is no statement of return shape. The scope constraint helps but does not fully compensate.

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 item_id parameter is documented with a concrete example (MLB4746731943), so the schema already does the work. The description adds no further meaning about the identifier format or source, which is acceptable at that coverage level.

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 both the content returned ('Preço e detalhe') and the resource ('um anúncio'), and the parenthetical adds a concrete scope constraint: only listings of the caller's own account, since 'a API nega anúncios de terceiros com este token.' It does not, however, distinguish this from siblings such as get_product, get_items, or get_item_description, leaving overlap unresolved.

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?

There is no when-to-use or when-not-to-use guidance and no reference to any sibling tool. The only guidance-like element is the negative constraint that third-party listings will be rejected, which is a restriction rather than a selection criterion. An agent must infer from the purpose alone when this tool is preferable to get_product or get_items.

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

Deploy Server

Other Tools