Skip to main content
Glama

manage_ads

Activate, pause, or check Mercado Libre Product Ads status for an item using seller and item IDs; optionally set a daily budget when activating.

Instructions

Gestiona Product Ads de Mercado Libre: activar, pausar o consultar estado de publicidad de un item.

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": {
      "seller_id": "<seller_id>",
      "item_id": "<item_id>",
      "action": "<action>"
    },
    "name": "manage_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAcción: "status" consulta el estado actual, "activate" activa publicidad, "pause" la pausa
item_idYesID de la publicación (ej: MLA1234567890)
seller_idYesID numérico del vendedor
daily_budgetNoPresupuesto diario en moneda local (solo para activate)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0-alpha.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a state-mutating operation for 'activate' and 'pause' with monetary consequences via daily_budget, yet says nothing about permission requirements, whether pausing discards budget or campaign settings, or whether activation is reversible. For a spend-affecting mutation tool with zero annotation coverage this is a significant gap.

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 front-loaded sentence that names the resource first and the operations second, with no filler. It is tightly packed but readable; the only cost is that compression leaves no room for the missing behavioral detail.

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

Completeness2/5

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

A mutation tool with a budget parameter, no annotations, and no output schema requires the description to explain effects and preconditions, and it does not. An agent knows what the tool is called but not what it changes, what it returns, or what could go wrong with the ad spend.

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 the action enum and the conditional nature of daily_budget ('solo para activate') fully documented in the schema. The description adds no parameter meaning beyond that, 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?

The description names a specific resource (Product Ads de Mercado Libre) and enumerates the three operations: activar, pausar, consultar estado. An agent can distinguish this from sibling tools like update_price or update_stock, which touch the listing itself rather than its advertising. It stops short of a 5 because it never explicitly contrasts itself with any named sibling.

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 three actions are listed, but there is no guidance on when to choose this tool over alternatives, no prerequisites (must the item be eligible for ads, must the listing be active?), and no mention of the financial commitment implied by activating ads. The agent must infer all usage context from the action enum alone.

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