Skip to main content
Glama
Sign In
Mercado Libre MCP Server

Mercado Libre MCP Server

by MarcosNahuel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_categories

Retrieve Mercado Libre categories and their attributes to identify the right category and required attributes when publishing products.

Instructions

Obtiene categorías de Mercado Libre y sus atributos. Útil para saber qué categoría usar al publicar y qué atributos son requeridos.

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_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoBuscar categoría por nombre (ej: "repuestos autos"). Usa el category predictor de ML.
category_idNoID de categoría específica (ej: MLA1234). Si se omite, lista las categorías raíz del sitio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0-alpha.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose return content (categories and their attributes), which is valuable given there is no output schema, but it says nothing about hierarchy depth, pagination, rate limits, or whether attributes are only populated for a specific category_id.

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?

Two short sentences with no filler: the first states what it returns, the second states why to call it. Purpose is front-loaded and 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 two-optional-parameter lookup with no annotations and no output schema, the description covers what is returned and the publishing use case. It omits how the two lookup modes differ behaviorally (name search vs. ID lookup vs. root listing) and gives no sense of result size or structure, which the agent must infer from the schema alone.

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%, with both parameters fully documented including examples and the root-listing fallback when category_id is omitted. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

"Obtiene categorías de Mercado Libre y sus atributos" names a specific verb (obtiene) and resource (categorías + atributos), so the agent knows exactly what the tool returns. It does not explicitly differentiate from siblings, but none of the listed siblings (get_orders, price_to_win, list_products, etc.) overlap with taxonomy lookup, so the gap is minor.

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 second sentence gives concrete usage context: use it to determine which category to publish in and which attributes are required. There is no when-not guidance or named alternative, but no plausible alternative exists among the siblings for category/attribute lookup.

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