MercadoLibre MCP Server

by dedero1985

Overview Schema Source Related Servers Discussions Admin

Get Order

get_order

Retrieve complete details for a specific MercadoLibre order by ID, including status, items, and buyer info. Specify site and account for accurate results.

Instructions

Get detailed information about a specific order.

Usage examples:

"Show me details for order 1234567890" → site_id="MLA" (or wherever the order lives)

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": {
      "input": "<input>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

C2.8/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 burden of behavioral disclosure. It conveys read-only intent by the word 'Get', but does not state side effects, authorization needs, error behavior, or that it does not mutate the order.

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?

The definition is short and front-loaded with its core purpose. The usage example is compact and useful, though the parenthetical 'or wherever the order lives' is vague and could be more explicit.

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?

Given that an output schema exists and the operation is nominally a simple getter, the definition is minimally adequate. However, it lacks usage-context information, especially whether to use search_orders when the order ID is unknown, and it does not specify how the site_id should be resolved.

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?

The description only gives a loose example mapping an order ID to site_id="MLA", and does not explain required order_id semantics or the optional account parameter. With schema description coverage listed at 0%, the description does very little to help an agent understand the parameters.

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?

The description states a specific operation: it gets detailed information about a single order. It is clearly different from listing or searching, but it does not explicitly differentiate itself from sibling tools like search_orders, so it lacks the explicit sibling contrast that would earn a 5.

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?

The description provides a usage example but no guidance about when to choose get_order over search_orders or other order-related tools. There is no when-to-use, when-not-to-use, prerequisites, or fallback guidance.

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