Skip to main content
Glama
Upload-Post

Upload-Post

Official

Resume an AutoDM rule

resume_autodm_rule
Idempotent

Resumes a paused account-wide AutoDM rule to restart automatic Instagram DMs for users who trigger it, and verifies the webhook subscription so delivery can resume.

Instructions

Resume a paused account-wide AutoDM rule, so it AUTOMATICALLY sends Instagram DMs as the user again to everyone who triggers it. Re-checks the Instagram webhook subscription: 502 webhook_subscription_failed means the user must reconnect Instagram; 409 rule_stopped (with stop_reason) means the Instagram account is no longer on that profile, so create a new rule instead.

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

Input Schema

NameRequiredDescriptionDefault
rule_idYesAutoDM rule ID (`rule_id` from list_autodm_rules or create_autodm_rule).

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare openWorldHint and idempotentHint but say nothing about side effects or failure modes; the description adds substantively by naming the webhook re-check and both error codes with their operational meaning. It stops short of saying what happens when the rule is already active, or whether DMs missed while paused are sent retroactively — meaningful gaps for a mutation with an automatic-send side effect.

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 primary action and its effect are front-loaded in the first clause, and the error-code guidance follows in a compact second sentence with no filler. The second sentence is dense with backticked codes, but each clause carries distinct operational 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?

With an output schema present and one fully documented parameter, the description covers the important unknowns: the side effect (automatic DM sending resumes), the webhook re-check, and both failure semantics. Only the already-active-rule behavior and the paused-state prerequisite are left unstated.

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?

There is a single parameter and schema coverage is 100%, with the schema itself documenting that `rule_id` comes from `list_autodm_rules` or `create_autodm_rule`. The description adds no format or sourcing detail beyond that, so the baseline 3 for fully documented schema 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 states a specific verb and resource ("Resume a paused account-wide AutoDM rule") plus the concrete effect (DMs resume sending automatically to everyone who triggers it), which distinguishes it from pause/delete/create siblings. It does not clarify how it differs from the sibling `resume_autodm`, so the reader cannot fully disambiguate within the resume family from the text 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?

It gives explicit routing for the failure paths: on 502 `webhook_subscription_failed` the user must reconnect Instagram, and on 409 `rule_stopped` the agent is told to create a new rule instead of retrying. That is real when-not guidance. Missing is any statement of prerequisites (rule must be paused) or a comparison to the `resume_autodm` sibling.

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

Deploy Server

Other Tools