Skip to main content
Glama
Upload-Post

Upload-Post

Official

List account-wide AutoDM rules

list_autodm_rules
Read-only

List an account's Instagram AutoDM rules to inspect status, triggers, keywords, reply stats, pending DMs, and webhook event delivery, so you can diagnose why a rule is not answering.

Instructions

List the account's Instagram AutoDM rules (the account-wide ones from create_autodm_rule; per-post monitors are in list_autodms). Each rule carries status (active, paused, reconnect_required, disabled, or stopped with a stop_reason such as account_disconnected), its triggers and keywords, stats per trigger (replies sent, skipped by cooldown, failed), DMs still pending in the queue, and a webhook block: subscribed, receiving_events, last_event_at, error and a hint. If receiving_events is false or error is set, Instagram is not delivering events and the rule cannot answer: tell the user, usually to reconnect Instagram.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_autodm_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_usernameNoOnly the rules of this Upload-Post profile.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.23.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the enumerated `status` values including reconnect_required/stopped with `stop_reason`, per-trigger `stats`, queued `pending` DMs, and the `webhook` health block with an interpretation rule. Strong added value, though the annotation bar makes a mid-high score appropriate rather than exceptional credit.

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 core purpose and the sibling disambiguation in the first clause, then the return-shape details. Dense but every clause carries information; the long second sentence packing status values, stats, queue and webhook fields is slightly unwieldy but not padded.

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?

Covers everything an agent needs: what is listed, how it differs from the sibling, enumerated status values, the webhook diagnostic fields, and what to do when events are not being delivered. An output schema exists, so return values are documented structurally, yet the description still supplies the interpretation guidance the schema cannot.

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 optional parameter (`profile_username`) with 100% schema description coverage, so the schema already carries its meaning. The description never mentions the parameter or what omitting it does (e.g., whether all profiles are returned), adding no meaning beyond the schema. Baseline 3 applies.

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 ("List the account's Instagram AutoDM rules") and immediately scopes it against a sibling: account-wide rules from create_autodm_rule versus per-post monitors in list_autodms. An agent can distinguish this from the similarly named sibling without opening either schema.

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?

Clear usage context: it returns rules plus health/diagnostic state, and it explicitly routes per-post monitors to list_autodms. It also gives actionable guidance ("If `receiving_events` is false or `error` is set ... tell the user, usually to reconnect Instagram"). It stops short of stating explicit exclusions versus log/history siblings like get_autodm_logs.

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