timers_listLists a StreamElements channel's bot timers to show messages posted on a schedule. Use it to review recurring bot announcements and scheduled chat messages.
List the channel's bot timers (messages the bot posts on a schedule).
| Name | Required | Description | Default |
|---|---|---|---|
| channel | No | StreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully defines 'timers' as scheduled messages, but adds nothing about pagination, ordering, return shape (no output schema), or whether all timers or only active ones are returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence with the core purpose front-loaded, and a compact parenthetical that adds real meaning without waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read-only list tool, the essentials are present, but without an output schema the description could say something about what is returned (e.g., timer id, name, interval). It is minimally complete rather than rich.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single optional 'channel' parameter is fully documented in the schema. The description adds no extra parameter meaning, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (channel's bot timers), and the parenthetical clarifies exactly what a timer is. It is easily distinguishable from siblings like timers_get, timers_create, and timers_update.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is the collection-level read operation, but it does not explicitly say when to use this instead of timers_get or how results relate to timers_create/update/delete. No exclusions or alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.