MCP Mercado Livre

get_category

Retrieve a category's name, root path, child categories, and listing constraints like max pictures and description length before creating an item.

Instructions

Get details of a category: its name, full path from the root, child categories (to keep drilling down the tree) and the listing settings that apply to it — including constraints relevant BEFORE create_item such as max pictures per item and max description length. A category with no children is a leaf and can be used as category_id in create_item; then call get_category_attributes for its mandatory attributes.

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": {
      "category_id": "<category_id>"
    },
    "name": "get_category"
  }
}

Input Schema

Name	Required	Description	Default
`category_id`	Yes	Category id, e.g. 'MLB1055' (from get_site_categories or predict_category)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the shape of the response (name, path, children, listing settings), the leaf/non-leaf semantic, and its place in the create_item workflow. It stops short of noting auth requirements, errors, or rate limits, but covers the behaviorally important parts.

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?

A single dense passage, front-loaded with what is returned and then the actionable workflow note. Every clause carries information, though it is slightly long and could be split into a return-value sentence and a usage sentence.

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?

There is no output schema and no annotations, so the description must explain returns and next steps; it does both (fields returned, leaf semantics, follow-up with get_category_attributes). Only minor gaps remain around pagination/limits or error cases, which are unlikely to matter for this lookup.

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% and the single category_id param is documented with an example format and its source tools (get_site_categories, predict_category). The description adds no parameter detail beyond the schema, 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 (get) and resource (category) and enumerates what details are returned: name, full path, child categories, and listing settings. It also clearly separates itself from siblings like get_site_categories (which lists) and get_category_attributes (which handles mandatory attributes).

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 routes the agent: a childless category is a leaf and can be used as category_id in create_item, then get_category_attributes should be called for mandatory attributes. It also flags that constraints must be read BEFORE create_item, giving concrete when-to-use and sequencing.

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