Skip to main content
Glama

Change an auto-reply

update_auto_reply
DestructiveIdempotent

Changes a rule: send only the fields to change. enabled=false pauses it at once. Turning a rule on, or changing what an enabled rule sends or where, first needs your human's OK in Shager, as in create_auto_reply (needs_confirmation with confirm_url, then the same call again). (Not available in an unclaimed sandbox.)

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>",
      "rule_id": "<rule_id>"
    },
    "name": "update_auto_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA short name the person will recognize, e.g. "Link in DM"
enabledNofalse (the default): the rule is saved paused. true: it starts answering real people, so it first needs your human's OK in Shager (needs_confirmation with confirm_url, then the same call again)
messageNoThe private message (to the commenter, or the answer to a direct message)
rule_idYes
triggerNoCOMMENT: someone comments on a post. MESSAGE: someone sends a direct message
keywordsNoWhole words or phrases, any case; empty = every comment or message
link_urlNoAdded at the end of the private message as a tracked short link
post_idsNoCOMMENT only: only comments on these Shager posts; empty = every post
channel_idsNoOnly these accounts; empty = every account that supports the trigger
workspace_idYesWorkspace id from list_workspaces
follow_buttonNofollowers_only: the button's text, up to 20 characters, e.g. "I'm following" (required with followers_only)
follow_promptNofollowers_only: the private reply asking them to follow and tap the button (required with followers_only)
followers_onlyNoCOMMENT only, Instagram only: the private reply is `follow_prompt` with a `follow_button`; when the person taps it, Shager asks Instagram whether they follow and sends `message` + `link_url` only to followers (others get `follow_reminder` with the button, up to 5 times). Accounts without follower_check in list_auto_replies skip these comments
public_repliesNoCOMMENT only: public answers under the comment, one picked at random
follow_reminderNofollowers_only: sent with the button again when they tap it without following yet; empty = follow_prompt again
once_per_personNoAnswer each person once per rule (30 days)
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.
attachment_media_idNoInstagram and Facebook: a file sent privately after `message`: an image (up to 8 MB), a video or a PDF (up to 25 MB) from this workspace's media (create_media_upload or upload_media_from_url first). On COMMENT rules the networks allow only text in the first private reply, so the private reply is `follow_prompt` with a `follow_button` and the file goes out when they tap it (with followers_only, only to followers). Accounts without `files` in list_auto_replies send the message without it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / attachment_media_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Instagram and Facebook: a file sent privately after `message`: an image (up to 8 MB), a video or a PDF (up to 25 MB) from this workspace's media (create_media_upload or upload_media_from_url first). On COMMENT rules the networks allow only text in the first private reply, so the private reply is `follow_prompt` with a `follow_button` and the file goes out when they tap it (with followers_only, only to followers). Accounts without `files` in list_auto_replies send the message without it"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / confirmation_token
      Added value: +{
      +  "description": "The confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.",
      +  "maxLength": 100,
      +  "type": "string"
      +}
    • changedInput schema / properties / enabled / description
      Previous value: -""New value: +"false (the default): the rule is saved paused. true: it starts answering real people, so it first needs your human's OK in Shager (needs_confirmation with confirm_url, then the same call again)"
  3. Changed4 schema fields changed
    • addedInput schema / properties / follow_button
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 20,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "followers_only: the button's text, up to 20 characters, e.g. \"I'm following\" (required with followers_only)"
      +}
    • addedInput schema / properties / follow_prompt
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 640,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "followers_only: the private reply asking them to follow and tap the button (required with followers_only)"
      +}
    • addedInput schema / properties / follow_reminder
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 640,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "followers_only: sent with the button again when they tap it without following yet; empty = follow_prompt again"
      +}
    • addedInput schema / properties / followers_only
      Added value: +{
      +  "description": "COMMENT only, Instagram only: the private reply is `follow_prompt` with a `follow_button`; when the person taps it, Shager asks Instagram whether they follow and sends `message` + `link_url` only to followers (others get `follow_reminder` with the button, up to 5 times). Accounts without follower_check in list_auto_replies skip these comments",
      +  "type": "boolean"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructive/openWorld/idempotent), it discloses the approval handshake (needs_confirmation with confirm_url, then the same call again), the immediate side effect of enabled=false, and the unclaimed-sandbox unavailability. These are exactly the behavioral details an agent cannot infer from structured fields.

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 the patch rule, then the immediate-pause effect, then the approval requirement, then the sandbox caveat. Dense and slightly packed with parentheticals, but 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 18-parameter destructive mutation with no output schema, it covers the critical behaviors: partial update, approval gating, immediate pause, and environment restriction. It omits what a successful response returns, but that is minor given the mutation is idempotent.

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 94%, so parameters are already well documented. The description reinforces patch semantics and the enabled flag but adds little field-level meaning the schema lacks; 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 a specific verb ('Changes') plus the partial-update contract ('send only the fields to change'), which lets an agent distinguish this patch operation from create_auto_reply/delete_auto_reply. The resource is called 'a rule' rather than 'auto-reply', but the title resolves that ambiguity.

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 operating context: patch semantics, that enabled=false pauses immediately, and that enabling or altering what an enabled rule sends/located requires human approval. It references create_auto_reply for the confirmation flow but does not explicitly route the agent away from delete_auto_reply for removal.

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