Skip to main content
Glama

Eurekuh

List DM auto-replies

list_dm_auto_replies
Read-onlyIdempotent

The organization's Instagram DM auto-replies: when someone sends one of the account's keywords in a DM, they get the reply (once a day per person). Also lists the Instagram accounts a rule can use.

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

Input Schema

NameRequiredDescriptionDefault
organizationIdNoWhich organization to act in: an id from list_organizations. Leave out for this connection's default organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: scope is organization-wide, a reply fires only once per day per person, and the call also surfaces the Instagram accounts a rule can use — an output characteristic that matters because no output schema exists.

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?

Two compact sentences with the resource front-loaded and no filler. The trailing 'Also lists the Instagram accounts a rule can use' is slightly ambiguous about whether it is part of the primary return payload, which keeps it from a 5.

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 a zero-required-parameter read tool with no output schema, the description supplies enough: what the records represent, the daily-per-person firing rule, and the extra accounts data returned. It omits ordering, pagination, and whether disabled rules are included, which are minor for this complexity level.

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 coverage is 100% and the single optional organizationId is fully described in the schema itself, including the default-organization fallback. The description adds nothing about the parameter, so the baseline 3 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 names the specific resource (Instagram DM auto-replies) and explains its domain meaning — keyword-triggered replies sent once per day per person — which goes beyond restating the title. However, it never uses an explicit retrieval verb, leaving the list/read action to be inferred from the name, and it does not distinguish itself from siblings like create_dm_auto_reply or delete_dm_auto_reply.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the read path before creating or toggling rules, but the description states no when-to-use condition, no exclusions, and does not name an alternative for a different need (e.g., listing accounts via list_accounts).

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