Skip to main content
Glama
Upload-Post

Upload-Post

Official

List AutoDMs and comment auto-replies

list_autodms
Read-only

Lists active per-post AutoDM and comment auto-reply monitors with platform, state, and counters; set include_inactive to include stopped or expired monitors.

Instructions

List the account's AutoDM and comment auto-reply monitors (one post each) with their platform, state and counters. Active ones only, unless include_inactive is true. Account-wide Instagram rules (every post, stories, DM keywords; no expiry) are listed by list_autodm_rules.

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_autodms"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_inactiveNoAlso list stopped and expired monitors.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.2

TDQS

A4.5/5.0
Behavior4/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 real behavioral context beyond that: the default filter excludes stopped and expired monitors, and the listed fields are platform, state and counters. It does not discuss pagination or result volume, which is the only remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and scope, followed by the filter rule and the sibling routing. No filler and nothing redundant with the title.

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?

An output schema exists, so return shape need not be explained, and annotations cover safety. With one fully documented optional parameter and an explicit pointer to the rules-listing sibling, nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter already carries a description, so the baseline would be 3. The description adds value by stating the default behavior (active only) that include_inactive overrides, which the schema alone does not state explicitly.

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 AutoDM and comment auto-reply monitors (one post each)', and immediately scopes the returned fields to platform, state and counters. The parenthetical '(one post each)' plus the explicit contrast with account-wide rules makes it distinguishable from list_autodm_rules without opening a 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?

Gives the default selection rule ('Active ones only, unless include_inactive is true') and routes the agent elsewhere for account-wide Instagram rules by naming list_autodm_rules. It lacks an explicit statement of the task this tool serves (e.g. auditing live monitors), so it stops short of full when/when-not guidance, but the alternative is clearly named.

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