Skip to main content
Glama

update_automation

Destructive

Change a comment-to-DM automation: pause or resume it (status), new keywords or match, a new DM text or public replies, new limits, or move it to another post (post_id, instagram_media_id or facebook_post_id). Only the fields you pass change. follow_gate true or false switches Follow first (Instagram) on or off and keeps its texts; new Follow first texts keep the switch as it is. follow_up false switches the follow-up off and keeps its texts; a new follow_up_text switches it on; follow_up_delay_hours, the button and the tap step texts alone change only themselves (null for the button removes it). The platform cannot change: to move to another channel (Instagram, the Facebook Page or X), create a new automation. Turning an X automation on (status 'active') needs X DMs on for the workspace, else 409 x_dms_off. A 'completed' automation starts again when its limits or trigger change.

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

Input Schema

NameRequiredDescriptionDefault
nameNoA label for the automations list, e.g. 'Free guide'.
matchNoword (default): the keyword stands on its own ('guide', 'Guide!' match; 'linkedin' does not match 'link'). contains: the keyword appears anywhere. any: every comment or message with text (ask the user before using it).
scopeNoFor the comment trigger (Instagram and Facebook; an X automation has no post): 'post' (default) = one post (pass post_id, instagram_media_id or facebook_post_id), 'next_post' = the next post the workspace publishes on this platform, 'any' = every post of the account or Page.
statusNo'paused' stops it without deleting it; 'active' resumes it (on X only while X DMs are on for the workspace).
dm_textNoThe DM sent to the person (max 1000 characters), once per person. On Facebook it lands in Messenger. On X, OmniSocials adds the line 'Reply STOP to stop automatic messages.' under it. Required on create. Confirm the text with the user before creating the automation: it goes out in the account's name.
post_idNoFor scope 'post' (Instagram and Facebook): the OmniSocials post id (from list_posts) that goes to the automation's platform. A scheduled post starts listening once it is live. One automation per post and platform: a post that goes to Instagram and Facebook can have one of each.
stop_atNoStop at this time (ISO 8601). null = no end.
keywordsNoKeywords that start the automation (up to 20, matched case-insensitively), e.g. ["guide", "link"]. Required unless match is 'any'.
platformNoWhere the automation runs: 'instagram' (default) = the connected Instagram account, 'facebook' = the connected Facebook Page (the DM lands in Messenger), 'x' = the connected X account (it answers DMs only; see create_automation). instagram_media_id implies 'instagram', facebook_post_id implies 'facebook'. It cannot change after create.
triggersNoWhat starts the automation. 'comment' (default on Instagram and Facebook) = a comment on an Instagram post or reel, or on a Facebook Page post; 'dm' = a keyword in a DM to the Instagram account, in a Messenger message to the Facebook Page, or in a DM to the X account; 'story_reply' = a keyword in a reply to an Instagram story (Instagram only: Facebook has no story replies). On X only 'dm' exists, and it is the default there. One automation can listen to several.
follow_upNoFollow-up (Instagram and Facebook): true = one more DM (follow_up_text) goes out follow_up_delay_hours after the answer. Meta allows an automatic message only within 24 hours after the person's last DM, button tap or quick reply, and a comment does not open that window: so on an Instagram comment (with Follow first off) the first DM becomes a tap step, a short message with one button (follow_up_tap_text, follow_up_tap_button), and the tap sends the DM text and opens the window; people who never tap get no link and no follow-up. A DM or story reply trigger needs no tap step. On Facebook only people who answer the DM get the follow-up. When it is due it is skipped if the person said stop, a team member answered them by hand, or their last tap or message is older than about 24 hours. false switches it off and keeps the texts. X has no follow-up: true there answers 400 follow_up_not_supported.
max_sendsNoStop after this many DMs (the automation becomes 'completed'). null = no limit.
follow_gateNoInstagram only. Follow first: true = the link (the DM text) goes out only to people who follow the account. On a comment the person first gets a short message with one button (follow_gate_text, follow_gate_button), and the public reply goes out at once as always; the tap makes OmniSocials ask Instagram whether they follow. A follower gets the DM text; anybody else gets not_following_text with its button and can tap again after following. On a DM or story reply trigger the check runs at once. When Instagram gives no answer the link goes out anyway. false switches it off and keeps the texts; the texts alone do not switch it on. Facebook and X have no follow status: true there answers 400 follow_gate_instagram_only.
automation_idYesThe automation id (from list_automations).
follow_up_textNoFollow-up: the message (max 1000 characters, 640 with a button). Giving it switches the follow-up on unless follow_up is false. Required to switch it on when none is stored. Confirm the text with the user: it goes out in the account's name.
public_repliesNoOptional public replies posted under the comment (one is picked at random per comment), e.g. ["Sent you a DM!", "Check your inbox"]. Comment trigger only (Instagram and Facebook; X has none). An empty array turns the public reply off.
facebook_post_idNoFor scope 'post' on Facebook: the id of a Facebook Page post that was NOT published through OmniSocials ({page-id}_{post-id}, or the post id alone). OmniSocials reads it from Facebook to check it belongs to the connected Page. Implies platform 'facebook'. Pass only one of post_id, instagram_media_id or facebook_post_id.
follow_gate_textNoFollow first: the first message, sent with one button (max 640 characters). Default: "Tap the button and I'll send you the link πŸ‘‡". Confirm the text with the user: it goes out in the account's name.
follow_gate_buttonNoFollow first: the label of the button on the first message (max 20 characters). Default: "Send me the link".
follow_up_tap_textNoFollow-up, Instagram only: the tap step's message, the first DM of a comment answer when Follow first is off (max 640 characters). Default: "Tap the button and I'll send you the link πŸ‘‡". Confirm the text with the user.
instagram_media_idNoFor scope 'post' on Instagram: the numeric Instagram media id of a post or reel that was NOT published through OmniSocials. OmniSocials reads it from Instagram to check it belongs to the connected account. Pass only one of post_id, instagram_media_id or facebook_post_id.
not_following_textNoFollow first: the answer to a tap from somebody who does not follow yet, sent with its own button (max 640 characters). Default: "Almost there! Follow us first, then tap the button again." Naming the account reads better, e.g. "Almost there! Follow @yourbrand first, then tap the button again." Confirm the text with the user: it goes out in the account's name.
follow_up_button_urlNoFollow-up: the web address of that button (https:// or http://, max 2000 characters). Pass it together with follow_up_button_title; null (either one) removes the button.
follow_up_tap_buttonNoFollow-up, Instagram only: the tap step's button label (max 20 characters). Default: "Send me the link".
not_following_buttonNoFollow first: the label of the button on that answer (max 20 characters). Default: "I follow now".
follow_up_delay_hoursNoFollow-up: hours after the answer went out, 1 to 23 (default 23, the end of Meta's 24-hour window).
follow_up_button_titleNoFollow-up: the label of an optional link button under the follow-up (max 20 characters). Pass it together with follow_up_button_url; null (either one) removes the button.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / follow_up
      Added value: +{
      +  "description": "Follow-up (Instagram and Facebook): true = one more DM (follow_up_text) goes out follow_up_delay_hours after the answer. Meta allows an automatic message only within 24 hours after the person's last DM, button tap or quick reply, and a comment does not open that window: so on an Instagram comment (with Follow first off) the first DM becomes a tap step, a short message with one button (follow_up_tap_text, follow_up_tap_button), and the tap sends the DM text and opens the window; people who never tap get no link and no follow-up. A DM or story reply trigger needs no tap step. On Facebook only people who answer the DM get the follow-up. When it is due it is skipped if the person said stop, a team member answered them by hand, or their last tap or message is older than about 24 hours. false switches it off and keeps the texts. X has no follow-up: true there answers 400 follow_up_not_supported.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / follow_up_button_title
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 20,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Follow-up: the label of an optional link button under the follow-up (max 20 characters). Pass it together with follow_up_button_url; null (either one) removes the button."
      +}
    • addedInput schema / properties / follow_up_button_url
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 2000,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Follow-up: the web address of that button (https:// or http://, max 2000 characters). Pass it together with follow_up_button_title; null (either one) removes the button."
      +}
    • addedInput schema / properties / follow_up_delay_hours
      Added value: +{
      +  "description": "Follow-up: hours after the answer went out, 1 to 23 (default 23, the end of Meta's 24-hour window).",
      +  "maximum": 23,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / follow_up_tap_button
      Added value: +{
      +  "description": "Follow-up, Instagram only: the tap step's button label (max 20 characters). Default: \"Send me the link\".",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / follow_up_tap_text
      Added value: +{
      +  "description": "Follow-up, Instagram only: the tap step's message, the first DM of a comment answer when Follow first is off (max 640 characters). Default: \"Tap the button and I'll send you the link πŸ‘‡\". Confirm the text with the user.",
      +  "maxLength": 640,
      +  "type": "string"
      +}
    • addedInput schema / properties / follow_up_text
      Added value: +{
      +  "description": "Follow-up: the message (max 1000 characters, 640 with a button). Giving it switches the follow-up on unless follow_up is false. Required to switch it on when none is stored. Confirm the text with the user: it goes out in the account's name.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / follow_gate
      Added value: +{
      +  "description": "Instagram only. Follow first: true = the link (the DM text) goes out only to people who follow the account. On a comment the person first gets a short message with one button (follow_gate_text, follow_gate_button), and the public reply goes out at once as always; the tap makes OmniSocials ask Instagram whether they follow. A follower gets the DM text; anybody else gets not_following_text with its button and can tap again after following. On a DM or story reply trigger the check runs at once. When Instagram gives no answer the link goes out anyway. false switches it off and keeps the texts; the texts alone do not switch it on. Facebook and X have no follow status: true there answers 400 follow_gate_instagram_only.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / follow_gate_button
      Added value: +{
      +  "description": "Follow first: the label of the button on the first message (max 20 characters). Default: \"Send me the link\".",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / follow_gate_text
      Added value: +{
      +  "description": "Follow first: the first message, sent with one button (max 640 characters). Default: \"Tap the button and I'll send you the link πŸ‘‡\". Confirm the text with the user: it goes out in the account's name.",
      +  "maxLength": 640,
      +  "type": "string"
      +}
    • addedInput schema / properties / not_following_button
      Added value: +{
      +  "description": "Follow first: the label of the button on that answer (max 20 characters). Default: \"I follow now\".",
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / not_following_text
      Added value: +{
      +  "description": "Follow first: the answer to a tap from somebody who does not follow yet, sent with its own button (max 640 characters). Default: \"Almost there! Follow us first, then tap the button again.\" Naming the account reads better, e.g. \"Almost there! Follow @yourbrand first, then tap the button again.\" Confirm the text with the user: it goes out in the account's name.",
      +  "maxLength": 640,
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / stop_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / stop_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  4. Changed8 schema fields changed
    • changedInput schema / properties / dm_text / description
      Previous value: -"The DM sent to the person (max 1000 characters), once per person. On Facebook it lands in Messenger. Required on create. Confirm the text with the user before creating the automation: it goes out in the account's name."New value: +"The DM sent to the person (max 1000 characters), once per person. On Facebook it lands in Messenger. On X, OmniSocials adds the line 'Reply STOP to stop automatic messages.' under it. Required on create. Confirm the text with the user before creating the automation: it goes out in the account's name."
    • changedInput schema / properties / platform / description
      Previous value: -"Where the automation runs: 'instagram' (default) = the connected Instagram account, 'facebook' = the connected Facebook Page (the DM lands in Messenger). instagram_media_id implies 'instagram', facebook_post_id implies 'facebook'. It cannot change after create."New value: +"Where the automation runs: 'instagram' (default) = the connected Instagram account, 'facebook' = the connected Facebook Page (the DM lands in Messenger), 'x' = the connected X account (it answers DMs only; see create_automation). instagram_media_id implies 'instagram', facebook_post_id implies 'facebook'. It cannot change after create."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "instagram",
      -  "facebook"
      -]New value: +[
      +  "instagram",
      +  "facebook",
      +  "x"
      +]
    • changedInput schema / properties / post_id / description
      Previous value: -"For scope 'post': the OmniSocials post id (from list_posts) that goes to the automation's platform. A scheduled post starts listening once it is live. One automation per post and platform: a post that goes to Instagram and Facebook can have one of each."New value: +"For scope 'post' (Instagram and Facebook): the OmniSocials post id (from list_posts) that goes to the automation's platform. A scheduled post starts listening once it is live. One automation per post and platform: a post that goes to Instagram and Facebook can have one of each."
    • changedInput schema / properties / public_replies / description
      Previous value: -"Optional public replies posted under the comment (one is picked at random per comment), e.g. [\"Sent you a DM!\", \"Check your inbox\"]. Comment trigger only. An empty array turns the public reply off."New value: +"Optional public replies posted under the comment (one is picked at random per comment), e.g. [\"Sent you a DM!\", \"Check your inbox\"]. Comment trigger only (Instagram and Facebook; X has none). An empty array turns the public reply off."
    • changedInput schema / properties / scope / description
      Previous value: -"For the comment trigger: 'post' (default) = one post (pass post_id, instagram_media_id or facebook_post_id), 'next_post' = the next post the workspace publishes on this platform, 'any' = every post of the account or Page."New value: +"For the comment trigger (Instagram and Facebook; an X automation has no post): 'post' (default) = one post (pass post_id, instagram_media_id or facebook_post_id), 'next_post' = the next post the workspace publishes on this platform, 'any' = every post of the account or Page."
    • changedInput schema / properties / status / description
      Previous value: -"'paused' stops it without deleting it; 'active' resumes it."New value: +"'paused' stops it without deleting it; 'active' resumes it (on X only while X DMs are on for the workspace)."
    • changedInput schema / properties / triggers / description
      Previous value: -"What starts the automation. 'comment' (default) = a comment on an Instagram post or reel, or on a Facebook Page post; 'dm' = a keyword in a DM to the Instagram account, or in a Messenger message to the Facebook Page; 'story_reply' = a keyword in a reply to an Instagram story (Instagram only: Facebook has no story replies). One automation can listen to several."New value: +"What starts the automation. 'comment' (default on Instagram and Facebook) = a comment on an Instagram post or reel, or on a Facebook Page post; 'dm' = a keyword in a DM to the Instagram account, in a Messenger message to the Facebook Page, or in a DM to the X account; 'story_reply' = a keyword in a reply to an Instagram story (Instagram only: Facebook has no story replies). On X only 'dm' exists, and it is the default there. One automation can listen to several."
  5. Changed7 schema fields changed
    • changedInput schema / properties / dm_text / description
      Previous value: -"The DM sent to the person (max 1000 characters), once per person. Required on create. Confirm the text with the user before creating the automation: it goes out in the account's name."New value: +"The DM sent to the person (max 1000 characters), once per person. On Facebook it lands in Messenger. Required on create. Confirm the text with the user before creating the automation: it goes out in the account's name."
    • addedInput schema / properties / facebook_post_id
      Added value: +{
      +  "description": "For scope 'post' on Facebook: the id of a Facebook Page post that was NOT published through OmniSocials ({page-id}_{post-id}, or the post id alone). OmniSocials reads it from Facebook to check it belongs to the connected Page. Implies platform 'facebook'. Pass only one of post_id, instagram_media_id or facebook_post_id.",
      +  "type": "string"
      +}
    • changedInput schema / properties / instagram_media_id / description
      Previous value: -"For scope 'post': the numeric Instagram media id of a post or reel that was NOT published through OmniSocials. OmniSocials reads it from Instagram to check it belongs to the connected account. Pass post_id OR instagram_media_id."New value: +"For scope 'post' on Instagram: the numeric Instagram media id of a post or reel that was NOT published through OmniSocials. OmniSocials reads it from Instagram to check it belongs to the connected account. Pass only one of post_id, instagram_media_id or facebook_post_id."
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Where the automation runs: 'instagram' (default) = the connected Instagram account, 'facebook' = the connected Facebook Page (the DM lands in Messenger). instagram_media_id implies 'instagram', facebook_post_id implies 'facebook'. It cannot change after create.",
      +  "enum": [
      +    "instagram",
      +    "facebook"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / post_id / description
      Previous value: -"For scope 'post': the OmniSocials post id (from list_posts) that goes to Instagram. A scheduled post starts listening once it is live. One automation per post."New value: +"For scope 'post': the OmniSocials post id (from list_posts) that goes to the automation's platform. A scheduled post starts listening once it is live. One automation per post and platform: a post that goes to Instagram and Facebook can have one of each."
    • changedInput schema / properties / scope / description
      Previous value: -"For the comment trigger: 'post' (default) = one post (pass post_id or instagram_media_id), 'next_post' = the next Instagram post the workspace publishes, 'any' = every post of the account."New value: +"For the comment trigger: 'post' (default) = one post (pass post_id, instagram_media_id or facebook_post_id), 'next_post' = the next post the workspace publishes on this platform, 'any' = every post of the account or Page."
    • changedInput schema / properties / triggers / description
      Previous value: -"What starts the automation. 'comment' (default) = a comment on an Instagram post or reel; 'dm' = a keyword in a DM to the account; 'story_reply' = a keyword in a reply to a story. One automation can listen to several."New value: +"What starts the automation. 'comment' (default) = a comment on an Instagram post or reel, or on a Facebook Page post; 'dm' = a keyword in a DM to the Instagram account, or in a Messenger message to the Facebook Page; 'story_reply' = a keyword in a reply to an Instagram story (Instagram only: Facebook has no story replies). One automation can listen to several."
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, yet the description still adds substantial behavior beyond them: cross-parameter side effects ('new follow_up_text switches it on'), null semantics ('null for the button removes it'), a concrete error code (409 x_dms_off), and the rule that a 'completed' automation restarts when limits or trigger change. This is exactly the mutation context an agent needs before calling.

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?

Purpose and the partial-update rule are front-loaded, and there is little pure filler. Some clauses are dense and semicolon-chained (the follow_gate sentence runs long), which costs readability, but every sentence carries operational content.

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 27-parameter mutation tool with no output schema, the description covers the platform immutability constraint, the X/Instagram/Facebook restrictions, error responses, and the accidental-null deletion behavior. Nothing an agent needs in order to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema documents each parameter individually; the description instead supplies the interactions the schema can't express, such as follow_gate true keeping its texts, follow_up false keeping texts while a new follow_up_text re-enables it, and follow_up_delay_hours/follow_up_tap_text changing only themselves. That is genuine cross-field meaning rather than restatement.

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?

Opens with a specific verb and resource ('Change a comment-to-DM automation') and immediately enumerates the editable dimensions: status, keywords/match, DM text, public replies, limits, and post move. An agent can distinguish this from create_automation or delete_automation from the first clause alone.

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?

Explicitly states 'Only the fields you pass change' and gives a clear when-not: 'The platform cannot change: to move to another channel... create a new automation.' It also covers re-activation of 'completed' automations and the X prerequisite. It stops short of naming delete_automation or get_automation as alternatives for other operations, but the scoping guidance is strong.

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