Skip to main content
Glama

retrigger_automation

Run an automation again over comments it already had the chance to answer: queues the recent comments on its posts back through the engine, so people whose comments came in while the automation was broken (an expired Instagram connection, a paused automation) get the DM and reply they should have.

THIS CAN SEND REAL DMS AND PUBLIC REPLIES to many people, so confirm with the user first — name the automation and what it sends (get_automation). Only an ACTIVE comment automation; it replays up to 5 posts x 250 recent comments. People who were already answered are not messaged again, and comments older than 7 days are skipped because Instagram refuses private replies to them. Raising a reply limit and retriggering also lets replies the limit suppressed go out now (resumed).

The comments are queued and handled in the background, so the effect shows up over the next minutes in get_automation_logs and the counters, not in this result. If the server cannot queue the work this refuses, changing nothing, and the user can use Retrigger in the reeldrop app.

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": {
      "workspace_id": "<workspace_id>",
      "automation_id": "<automation_id>"
    },
    "name": "retrigger_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
automation_idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
queuedYes
resumedYes
submittedYes
skipped_too_oldYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, and the description substantially enriches those hints: it warns this can send real DMs and public replies, caps the replay at 5 posts x 250 recent comments, explains the 7-day skip for Instagram private replies, notes already-answered people are not re-messaged, and discloses that work is queued in the background rather than in the result. The only remaining gap is that it does not tie the behavior to idempotentHint=false (repeated calls may re-queue) or to the openWorld nature of the Instagram dependency. Not treating the 'sends real messages' warning as running counter to destructiveHint=false, since that hint conventionally covers data destruction, not outbound messaging.

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 purpose, then the safety warning, then the constraints and the background-processing caveat in a sensible order; every sentence carries operational information. It is a bit long and the parenthetical stacked details (5 posts x 250 comments, the 7-day rule) make it dense, but nothing is clearly expendable.

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 side-effecting replay tool this covers the essentials: safety confirmation, eligibility constraints, replay limits, dedupe and age exclusions, asynchronous behavior, and failure semantics (refuses and changes nothing). An output schema exists, so the description need not explain return values, and it correctly points to get_automation_logs and counters for observing effects.

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?

Schema description coverage is 0% for the two required parameters, so the description carries the full burden: it implies automation_id must identify an active comment automation, but workspace_id is never mentioned and neither parameter is named, typed, or given format expectations. It adds some useful domain semantics (ACTIVE comment automation only) yet leaves half the input surface undocumented.

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?

The description opens with a specific verb-and-resource framing ('Run an automation again over comments it already had the chance to answer') and immediately scopes it to a re-run over already-existing comments, which separates it cleanly from create_automation, update_automation, and preview_automation without requiring the reader to open any schema.

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?

It states when to use it (comments that arrived while the automation was broken, e.g. an expired Instagram connection or a paused automation), the key prerequisite (only an ACTIVE comment automation), a mandatory confirmation step with a pointer to get_automation, and an explicit fallback ('Retrigger in the reeldrop app') if the server refuses.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources