Iris

create_responder_comment_trigger

Destructive

create a comment trigger. when someone comments the keyword on the account's instagram post, iris sends that person one direct message: the owner's message as written, followed by the notice that it is automated. instagram allows one such message per comment, within 7 days of the comment, and nothing more unless the person replies. it only sends while status.comment_triggers on get_responder is ready; needs_permission means the owner has to reconnect instagram from the responder settings page in the iris web app, unavailable means the feature isn't offered on the account yet. each message sent counts as a message against the plan. needs an API key and a connected instagram account; x402 and MPP identities cannot use it. at most 20 triggers per account, and a second trigger with the same keyword on the same post is refused. requires write scope.

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": {
      "keyword": "<keyword>",
      "message": "<message>"
    },
    "name": "create_responder_comment_trigger"
  }
}

Input Schema

Name	Required	Description
`enabled`	No	whether the trigger is active (default true)
`keyword`	Yes	matched as a whole word or phrase in the comment, case-insensitive (1-50 characters)
`message`	Yes	the DM sent to the commenter, before the automated notice (1-900 characters, and at most 700 bytes)
`media_id`	No	the numeric instagram media id to limit the trigger to one post (5-40 digits; get it from list_responder_posts); omit or send null to match every post

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes far beyond the destructiveHint=true annotation by disclosing the Instagram platform limit (one automated message per comment, within 7 days, nothing more unless the person replies), plan billing impact (each message counts against the plan), identity exclusions (x402 and MPP cannot use it), and hard caps (20 triggers per account, duplicate keyword+post refused). This is exactly the operational context an agent needs before invoking a write tool.

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 action and mechanism, then progressively adds gating, limits, and auth. Dense but nearly every clause carries actionable information; the run-on lowercase phrasing slightly hurts scanability but there is little filler.

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 mutation tool with no output schema, the description covers behavior, failure modes, quotas, and auth thoroughly. It does not state what is returned on success (e.g., the new trigger's identifier), which is the main remaining gap for an agent chaining a follow-up call.

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 description coverage is 100%, so keyword, message, media_id, and enabled are already fully documented including length and byte constraints. The description reinforces that the keyword is matched on a post comment and that media_id scopes to one post, but adds no format or constraint detail the schema does not already carry.

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?

Opens with a specific verb+resource ("create a comment trigger") and immediately describes the exact mechanism: a commenter matching a keyword on an Instagram post receives one DM. The creation semantics are unambiguous and clearly distinct from the list/update/delete siblings named in the catalog.

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 concrete preconditions for use: the account's status.comment_triggers must be "ready", with "needs_permission" and "unavailable" states explained, plus API key, connected Instagram account, and write scope requirements. It does not explicitly route to update_responder_comment_trigger for modifying an existing trigger, so it stops short of full when/when-not guidance.

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

All Iris tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?