Skip to main content
Glama
Mercado Libre MCP

Mercado Libre MCP

by fedeclavero

meli_user_product_stock

Read-only

Retrieve distributed stock levels and warehouse locations for a Mercado Libre user product to identify where inventory is held; note that Full fulfillment stock may not be editable.

Instructions

Consulta stock distribuido y ubicaciones; Full puede no ser editable.

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": {
      "user_product_id": "<user_product_id>"
    },
    "name": "meli_user_product_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds a real behavioral nuance, that stock for 'Full' (fulfillment) may not be editable, which the annotations do not convey. It says nothing about pagination, response shape, or whether stock is per-warehouse.

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

Conciseness3/5

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

Very short and front-loaded, but the semicolon-joined second clause is cryptic rather than informative. Brevity here reflects under-specification rather than disciplined concision.

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?

No output schema exists, so the description should disclose that the response contains stock levels and location/warehouse data — it only alludes to this in Spanish shorthand. Combined with an undocumented required parameter, an agent lacks enough to call this correctly on the first try.

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 description coverage is 0% and the single required parameter user_product_id is never mentioned or explained in the description. With one undocumented parameter the description must compensate and does not — it gives no hint that the ID is a user-product identifier or where to obtain it.

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

Purpose3/5

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

States a verb and resource ('Consulta stock distribuido y ubicaciones') so the basic purpose is inferable, but 'distribuido' and the relationship to the sibling meli_user_product are unexplained. An agent cannot tell from the description whether this returns per-warehouse stock for a user product or something else.

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?

No statement of when to use this versus the closely named sibling meli_user_product, and no prerequisites stated. The only usage-adjacent hint ('Full puede no ser editable') is a vague caveat rather than routing guidance.

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