MCP Mercado Livre

update_item

Update an existing Mercado Livre listing's price, stock, title, or video. Use for price changes and stock adjustments; visibility changes require a separate status tool.

Instructions

Update mutable fields of an existing listing owned by the authenticated seller: price, stock (available_quantity), title or video. Use this for price changes and stock adjustments; to change visibility (pause/activate/close) use update_item_status instead. Only the provided fields are sent. Gotcha: the title can only be changed while the item has no sales — once units are sold, Meli rejects title updates. Returns the updated item id, price, available_quantity and status.

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

Input Schema

Name	Required	Description
`price`	No	New sale price
`title`	No	New title (max 60 chars); only allowed while the item has no sales
`item_id`	Yes	Full item id with site prefix, e.g. 'MLB123456789'
`video_id`	No	Id of a video previously uploaded to the seller's account
`available_quantity`	No	New stock quantity

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers real behavioral context: partial-update semantics ('Only the provided fields are sent') and a non-obvious business rule (title updates rejected once units are sold). It stops short of stating auth/permission requirements or failure/reversibility behavior, so it is strong but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Front-loads the core purpose, then the sibling routing rule, then the gotcha, then the return shape, in four dense sentences with no filler. Every sentence earns its place.

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

Completeness4/5

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

No output schema exists, and the description compensates by naming the returned fields (id, price, available_quantity, status). It covers partial-update semantics and the key business constraint; only permission/error-handling context is absent, which is a minor gap for a mutation tool.

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%, so every parameter is already documented in the schema, including the title's no-sales constraint and the site-prefixed item_id format. The description adds little beyond restating field names, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (update) and resource (an existing listing owned by the authenticated seller) and enumerates the mutable fields: price, stock, title, video. It explicitly distinguishes itself from the sibling update_item_status, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicitly names when to use it ('price changes and stock adjustments') and when to use the alternative instead ('to change visibility (pause/activate/close) use update_item_status'). This is the when/when-not/alternative pattern at full strength.

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