chatgenius

list_comment_triggers

Read-onlyIdempotent

List comment triggers. Standalone comment triggers, newest first, each with the flows linked to it. A flow whose own trigger node carries keywords (native) is not a trigger and appears only on /flows as a comment source with mode native.

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

Input Schema

Name	Required	Description
`limit`	No	Page size, 1 to 100. Default 25.
`active`	No	true for live triggers only, false for paused.
`post_id`	No	Triggers scoped to this post.
`platform`	No	Triggers that fire on this channel (a both trigger matches either).
`source_type`	No	What the trigger listens to.
`starting_after`	No	The next_cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavior: results are ordered newest first and each entry is joined with its linked flows, which an agent cannot infer from the schema. The native-trigger exclusion is also scope-relevant, though phrased in a way that takes effort to parse.

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

Conciseness3/5

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

The core scope is front-loaded in the first two sentences, which earns the opening. The third sentence is a single 30-plus-word clause with an aside in parentheses and a raw path reference ('/flows', 'mode native'), which reads as internal spec leakage rather than agent-facing guidance.

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?

With no output schema, the description sensibly discloses the return shape (triggers plus linked flows) and ordering, which is what an agent needs before iterating. Pagination is handled by the documented starting_after parameter, so the remaining gap is minor; only the confusing native-trigger wording weakens it.

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% and each of the six parameters, including the two enums, is already documented in-schema. The description adds no filter semantics beyond what the schema provides, so the baseline of 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?

First sentence states a specific verb and resource ('List comment triggers') and the second narrows the scope to 'Standalone comment triggers, newest first, each with the flows linked to it.' It is distinguishable from get_comment_trigger and from list_flows by the standalone qualifier, though the scope distinction is buried in a dense third sentence.

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?

There is an implied when-not: flow-embedded 'native' triggers are excluded and live on /flows instead, which routes the agent in one direction. However, nothing says when to prefer this over get_comment_trigger, get_comment_trigger_stats, or list_flows, and no prerequisites or pagination guidance are given.

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

All chatgenius 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?