Skip to main content
Glama

Update automation

update_automation
DestructiveIdempotent

Replaces all settings and messages of an automation (send the complete automation, not just the changes). Its status stays as it is. If the automation is live, changes reach real people right away, so confirm with the creator first.

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": {
      "trigger": "<trigger>",
      "link": "<link>",
      "id": "<id>"
    },
    "name": "update_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAutomation id from list_automations.
linkYesThe main DM.
openingNoOptional first DM with a button. When the person taps the button, the link message follows. Recommended: Instagram only lets Pidgo keep talking (follow gate, email, follow-up) after the person answers.
post_idNoInstagram media id from list_posts. Required when trigger is 'post'.
triggerYes'post': comments on one post (needs post_id). 'any': comments on any post. 'next': the next post the creator publishes. 'live': comments during an Instagram Live (no public reply). 'story': replies to any of the creator's stories. 'dm': a DM with the keyword. 'mention': someone mentions the creator in their story (no keywords). story, dm and mention start in the DMs: no public_reply and no opening; follow_gate, email_question and followup work without opening.
followupNoOptional reminder some hours later. Needs opening, except for story, dm and mention.
keywordsNoWords in a comment that start the automation, e.g. ['GUIDE']. Matching ignores case. Up to 20, each up to 30 characters.
any_keywordNoTrue to react to every comment, whatever it says. Then keywords are ignored.
follow_gateNoOptional: only send the link to people who follow the creator. Needs opening, except for story, dm and mention.
public_replyNoOptional public reply under the comment, e.g. 'Check your DMs!'. Max 300 characters.
email_questionNoOptional: ask for the person's email address before the link. Needs opening, except for story, dm and mention.
public_reply_variantsNoOptional: up to 3 other wordings of this message (max 300 characters each). Pidgo picks one at random every time, so the replies don't all look the same. Left out on update_automation, the current ones stay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, and the description adds real context beyond that: full replacement (omitted content is overwritten), status is preserved, and changes on a live automation reach real people immediately with an instruction to confirm with the creator. What it does not resolve is how "replaces all settings" squares with the schema's repeated note that omitted variants "stay" — that ambiguity about what is actually destroyed is the one 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?

Three short sentences, front-loaded with the behavior that matters most (full replacement), then the status invariant, then the risk warning. Nothing is padded, though the live-warning sentence could be folded in without loss.

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 a 12-parameter destructive mutation with nested objects and no output schema, the description covers the essential stakes and the replace contract, which is what an agent most needs before writing. It stops short of saying what a successful call returns or whether omitted optional fields are cleared or retained, leaving the main operational ambiguity unaddressed.

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 every parameter including the trigger enum and nested link/opening/followup objects is already documented in the schema. The description adds no syntax, format, or defaulting detail beyond the replace-all rule, which justifies the baseline rather than a higher score.

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 ("Replaces all settings and messages of an automation") and immediately pins down the replace-not-patch semantics with "send the complete automation, not just the changes." That single clause distinguishes it from any partial-update behavior an agent might otherwise assume, so no sibling name is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear conditional instruction for one case — if the automation is live, confirm with the creator first — and "Its status stays as it is" implicitly steers an agent to pause_automation for status changes. But it never explicitly says when to choose this over create_automation or what to do when the agent lacks full state (e.g., fetch with get_automation first). Useful but partial routing guidance.

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