Skip to main content
Glama
Mercado Libre MCP

Mercado Libre MCP

by fedeclavero

meli_set_item_pictures

Destructive

Replaces an item's entire picture list with public HTTPS URLs; include all pictures that must be kept to avoid losing existing images.

Instructions

Reemplaza la lista completa de fotos usando URLs HTTPS públicas; incluye todas las fotos que deban conservarse.

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>",
      "picture_urls": "<picture_urls>"
    },
    "name": "meli_set_item_pictures"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
picture_urlsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is partly covered; the description still adds the crucial non-obvious detail that this is a full replacement rather than an append, plus the HTTPS-public-URL constraint. It omits return behavior and error handling for invalid URLs (relevant given the meli_picture_errors sibling).

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?

A single compact sentence with the destructive replacement semantics front-loaded, then the retention caveat. 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 destructive two-parameter write with no output schema and 0% parameter documentation, the description covers the replacement semantics and URL requirement but leaves the agent without guidance on failure modes, limits, or what the response contains. Adequate but with clear gaps.

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 coverage is 0%, so the description must compensate: it does add meaning for picture_urls (must be public HTTPS URLs) and implies full-list semantics, but it never explains item_id or array ordering/max-count constraints. It covers one of two parameters meaningfully.

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 verb and resource ('Reemplaza la lista completa de fotos') that clearly identifies a mutation of an item's photo list. It distinguishes the operation from read-side picture siblings like meli_picture_errors implicitly through the 'Reemplaza' verb, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

The clause 'incluye todas las fotos que deban conservarse' gives the essential usage condition for a full-replacement call (you must resend the ones you want to keep). It does not name an alternative tool or mention prerequisites/auth, so it stops short of explicit when/when-not routing.

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