Skip to main content
Glama
Sign In
Mercado Libre MCP Server

Mercado Libre MCP Server

by MarcosNahuel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_products

Retrieve a seller's Mercado Libre products with title, price, stock, status, link, and thumbnail; filter by status and paginate results.

Instructions

Lista los productos/publicaciones de un vendedor en Mercado Libre. Retorna título, precio, stock, estado, link y thumbnail.

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": {
      "seller_id": "<seller_id>"
    },
    "name": "list_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCantidad máxima de productos (default 50)
offsetNoOffset para paginación
statusNoFiltrar por estado de la publicación
seller_idYesID numérico del vendedor en ML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0-alpha.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It names the returned fields (title, price, stock, status, link, thumbnail), which helps, but says nothing about pagination semantics, default result size, authentication requirements, rate limits, or whether all publication states are included when no filter is set.

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 sentences, zero filler, with the purpose front-loaded and the return shape second. The field enumeration earns its place because there is no output schema.

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 simple 4-parameter list tool with no output schema, the description covers purpose and return fields, and the schema covers all parameters. However, with no annotations at all, it should also disclose read-only nature and pagination behavior to be fully self-sufficient.

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 limit, offset, status and seller_id are all documented in the schema itself. The description adds no additional meaning about parameters beyond mentioning 'estado' as a returned field rather than a filter. Baseline 3 applies when the schema does the heavy lifting.

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: 'Lista los productos/publicaciones de un vendedor en Mercado Libre'. An agent can tell this retrieves a seller's catalog, which separates it from siblings like get_item_metrics or search_competitors, though no sibling is named 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 by the scope phrase 'de un vendedor'; there is no statement of when to prefer this over search_competitors or get_item_metrics, nor any prerequisite such as needing a valid seller_id. Adequate but leaves routing to inference.

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