mercadolivre-mcp

Meus anúncios

get_own_items

Retrieves the authenticated seller's own Mercado Livre listings with prices and details, with pagination and status filters. Use it to access your account's ads, since the API only lists your own.

Instructions

Anúncios da própria conta (dona do token) com preço e detalhes. A API do ML só permite listar a própria conta.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_own_items"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`status`	No	active, paused, closed...	active
`details`	No	inclui preço/detalhes via bulk

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

C2.9/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 and it does not do so. It discloses that price/details come back and that the API constrains results to the token owner, but says nothing about read-only nature, pagination behavior, result caps, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler. The scoping statement is placed immediately after the purpose statement, which is the right order for an agent scanning the description.

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

Completeness2/5

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

With four parameters, no output schema and no annotations, the description is too thin to call correctly without opening the schema. It omits pagination expectations, return shape, and any safety/auth context for what is effectively an authenticated listing call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (limit and offset are undocumented), and the description never mentions any parameter. 'com preço e detalhes' loosely echoes the details flag but gives no guidance on limit/offset/status semantics or defaults, so it does not compensate for the coverage gap.

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 and scope: listings belonging to the token's own account, with price and details. The phrase 'própria conta (dona do token)' distinguishes it from the generic listing siblings like get_items or search_products, though it never names an alternative explicitly.

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: 'A API do ML só permite listar a própria conta' hints at when this tool applies (you want your own listings, not arbitrary ones). There is no explicit when-to-use/when-not or pointer to a sibling for marketplace-wide search.

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

Deploy Server