MCP Mercado Livre

send_message

Sends a post-sale message to a Mercado Livre buyer for a specific order after confirming the text; read prior order messages first for context.

Instructions

Send a post-sale message to the buyer of a specific order — this is a REAL message delivered to the buyer, so confirm the exact text with the user before sending. Only for post-sale communication tied to an order. Important Mercado Livre moderation rules: messages are moderated and must NOT contain contact information — no links, phone numbers, e-mails or social media handles; violations can lead to sanctions on the seller's account, up to suspension. Text is limited to 350 characters. Use get_order_messages first to read the conversation context. Returns the sent message id, moderation status and date.

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": {
      "order_id": "<order_id>",
      "text": "<text>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Message text, max 350 characters; no links, phone numbers or e-mails (moderated)
`order_id`	Yes	Numeric order id from get_orders

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

A4.4/5.0

Behavior5/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 and does so thoroughly. It discloses that this is a REAL buyer-facing message, requires user confirmation, is subject to Mercado Livre moderation with account suspension risk, forbids contact information, is limited to 350 characters, and returns message id, moderation status, and date.

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 description is front-loaded with the core action and then layers in critical warnings, prerequisites, and return information. It is somewhat long and repeats the schema's character limit and moderation warning, but every major sentence contributes useful guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is complete: it covers side effects, moderation rules, user confirmation, prerequisite context lookup, and return values. An agent has enough information to call it safely and correctly.

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 the baseline is 3. The description reiterates the text limit and moderation constraint already in the schema, and adds little new syntax or meaning for order_id beyond what is already documented.

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 and resource: send a post-sale message to the buyer of a specific order. It distinguishes itself from sibling read tools like get_order_messages by being the send action, and from claim messaging by restricting to post-sale communication tied to an order.

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?

Gives clear usage context: only for post-sale communication tied to an order, confirm exact text with the user before sending, and use get_order_messages first for context. It does not explicitly name send_claim_message as the alternative for claim-related messages, but the scoping exclusion is strong.

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