Skip to main content
Glama
Sign In

Breakreach

by com.breakreach
OverviewDiscussionsAdmin

Create Comment to DM rule

create_comment_dm_rule

Set up a Comment to DM automation on an Instagram account or a Facebook Page: when someone comments one of the keywords on the post (or on any post of the account), Breakreach sends them the DM through a private reply (Instagram Direct, or Messenger from the Page), and can post a public reply under their comment. Both networks allow one private reply per comment within 7 days; each person gets the DM once per rule. Target a post with mediaId (the Instagram or Facebook post id, e.g. postId from list_recent_comments) or postId (a Breakreach post published on that account); omit both for every post. Needs a Pro or Agency plan on the workspace.

Input Schema

NameRequiredDescriptionDefault
matchNocontains (default) = the keyword appears as a whole word or phrase in the comment; exact = the comment is just the keyword
activeNofalse pauses the rule
dmTextYesThe DM sent to the person who commented (up to 1000 characters, links allowed). {username} becomes their @handle on Instagram, their first name on Facebook
postIdNoA Breakreach post id (from list_posts) published on this account, instead of mediaId
mediaIdNoInstagram or Facebook post id (postId in list_recent_comments). Omit, with postId, for every post of the account
keywordsNoWords or phrases that trigger the DM (up to 20). Case and accents are ignored. Empty or omitted = every comment triggers it
accountIdYesInstagram account or Facebook Page id from list_accounts
workspaceNoWorkspace slug (optional)
publicRepliesNoOptional public replies posted under the comment once the DM is sent, one picked at random (up to 5), e.g. "Sent! Check your DMs". {username} becomes their @handle on Instagram, their first name on Facebook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare only write/open-world safety hints, yet the description adds real operational constraints: one private reply per comment within 7 days, one DM per person per rule, and the required plan tier. These are behavioral facts an agent cannot derive from the structured fields.

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?

A single dense paragraph that is front-loaded with the automation's effect before the targeting rules. Every clause carries information, though the run-on structure and repetition of the {username} substitution (also in the schema) make it slightly heavier than necessary.

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?

For a 9-parameter mutation tool with no output schema and annotations covering only safety, the description supplies the missing context: trigger semantics, delivery limits, network differences, and plan requirement. An agent has enough to call it correctly without further inference.

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 baseline is 3, but the description adds cross-parameter semantics that the per-field schema does not: mediaId and postId are mutually exclusive alternatives, and omitting both applies the rule to every post. That relationship-level guidance pushes it above baseline.

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+resource (set up a Comment to DM automation) and specifies the two supported networks, Instagram accounts and Facebook Pages. The trigger/action mechanics (comment keyword -> private reply DM + optional public reply) clearly separate it from create_dm_automation and reply_to_comment.

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?

Explains the context in which to use it and that the workspace needs a Pro or Agency plan, plus which targets apply (mediaId vs postId vs omit both). It lacks an explicit when-not statement or a named alternative sibling, so it stops short of a 5.

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

All Breakreach toolsInspect
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