Skip to main content
Glama

Agenda comercial y cronograma de MercadoLibre

ml_agenda
Read-only

Manage MercadoLibre Colombia campaign and promotion calendar: review upcoming dates, decide participation, confirm or add dates, and get page update kits.

Instructions

La agenda de Clara (del equipo de trabajadores): las fechas cruciales del año (Hot Sale, CyberMonday, Black Friday, Día de la Madre/Padre/Infancias, Navidad…) y el cronograma de campañas y promociones que MercadoLibre te ofrece, con cierre de inscripción, candidatas y si ya participás. Por cada una pregunta SIEMPRE si querés participar y guarda tu decisión (no se inscribe sola: inscribir es con ml_aceptar_promocion y tu OK). Acciones: calendario (lo que viene), decidir (sí/no a una campaña o fecha), fecha (confirmar una fecha estimada o agregar una propia), pagina (el kit para actualizar Mi página: banner y productos a destacar del evento).

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": {
      "accion": "<accion>"
    },
    "name": "ml_agenda"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNodecidir: el id que muestra el calendario (ej: P-HOT, cybermonday:2026, propia:aniversario) · fecha: la clave de la fecha estimada a confirmar (ej: cybermonday:2026)
diasNocalendario: cuántos días hacia adelante (default 60, máx 365)
notaNodecidir: por qué (ej: "solo con los termos")
fechaNofecha: AAAA-MM-DD
accionYesQué hacer
cuentaNouser_id de la cuenta de ML si hay varias conectadas (ver ml_cuentas)
nombreNofecha: nombre de una fecha propia (ej: "Aniversario de la tienda")
participarNodecidir: true = sí participo, false = no participo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0-tyl.1

TDQS

A3.5/5.0
Behavior2/5

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

The description adds genuinely useful behavior: the tool never self-enrolls, it only records the user's decision, and enrolment requires ml_aceptar_promocion plus explicit user OK. But annotations declare readOnlyHint=true while the description says it 'guarda tu decisión', i.e. it persists state — a read-only claim for a tool with a write action. The contradiction is partial (calendario/fecha are reads, decidir writes) and the description is transparent about it, but it conflicts with the structured hint.

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?

Front-loaded with what the agenda contains, then the mandatory ask-and-record rule, then the four actions — a sensible order. It is dense and parenthesis-heavy (persona 'Clara', date lists), but nearly every clause carries actionable information.

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?

For an 8-parameter, multi-action tool with no output schema, the description covers all four actions, the required user-confirmation flow, and the hand-off to ml_aceptar_promocion. Remaining gaps (return shape of calendario, whether decidir is idempotent or how cuenta-scoped decisions persist) are minor given the action enum is fully documented in the schema.

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 each parameter already documents its action (ref, dias, nota, fecha, nombre, participar, cuenta). The description only restates the action names and hints at inputs like 'confirmar una fecha estimada o agregar una propia', adding no formats, defaults or constraints beyond the schema. Baseline 3 is appropriate.

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 concretely what the resource is (the commercial agenda: key dates like Hot Sale/CyberMonday/Black Friday and the campaign schedule with sign-up windows, candidates and participation status) and then enumerates its four actions (calendario, decidir, fecha, pagina). An agent can distinguish it from ml_promociones or ml_aceptar_promocion, though the multi-action nature makes it a slightly sprawling purpose rather than a single verb+resource.

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?

Explicit behavioral rule: 'pregunta SIEMPRE si querés participar y guarda tu decisión (no se inscribe sola: inscribir es con ml_aceptar_promocion y tu OK)' — it names the alternative tool and the condition that selects it. It also maps each action to its purpose. It does not, however, say when to prefer this over ml_promociones or ml_tablero for general promo questions.

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