Skip to main content
Glama

Eurekuh

Create a DM auto-reply

create_dm_auto_reply
Destructive

Add an Instagram DM auto-reply: anyone who DMs keyword to the account gets reply automatically, at most once a day each.

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": {
      "accountId": "<accountId>",
      "keyword": "<keyword>",
      "reply": "<reply>"
    },
    "name": "create_dm_auto_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
replyYesThe DM sent back, up to 1000 characters.
keywordYesOne word, e.g. "LINK". Case doesn't matter.
accountIdYesThe Instagram account id, from list_dm_auto_replies or list_accounts.
replyAltsNoOptional other versions of reply (up to 9); each person gets one at random.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, destructive, non-idempotent, open-world write. The description adds genuine behavior beyond that: the trigger model (keyword match in an inbound DM) and a throttling rule (at most once per day per person). It still omits failure behavior on duplicate keywords and any permission/scope requirements, which is why it is not a 5.

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?

One sentence, front-loaded with the action, and every clause carries information: trigger, automated response, and rate limit. No filler or restatement of the title.

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 5-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, trigger, and throttle. What is missing is conflict handling (duplicate keyword for the same account) and confirmation of the initial enabled state, both of which an agent would want before calling a destructive create.

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%, so the baseline is 3, but the description adds real meaning by framing keyword as a trigger term that inbound DMs must match rather than an arbitrary label, and by tying the reply to a per-person daily cap. The accountId provenance pointer in the schema already covers sourcing, so the remaining gap is minor.

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?

"Add an Instagram DM auto-reply" names a specific verb (add) and resource, then spells out the operational contract: anyone DMing the keyword gets the reply. The create verb plus the DM-auto-reply resource cleanly separates it from delete_dm_auto_reply, set_dm_auto_reply_enabled, and list_dm_auto_replies without needing to name them.

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 implied by the trigger description, and the accountId field points to list_dm_auto_replies / list_accounts as the source of ids. However, there is no explicit when-to-use versus when-not guidance, no mention of what happens if a keyword already exists, and no statement about whether the new rule is enabled immediately (which matters given the sibling set_dm_auto_reply_enabled).

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