songrequests_nextRetrieves the next song in a StreamElements media request queue, letting AI assistants inspect or manage upcoming song requests for a channel.
Get the next song in the media request queue.
| 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 declare readOnlyHint=true, so the safety profile is already covered, and the description is consistent with it (no mutation implied). It adds only that the song comes from a queue, without saying whether the item is consumed/removed or what happens when the queue is empty.
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?
A single short, front-loaded sentence with no filler. It is efficient, though it is arguably too terse to carry its routing burden.
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?
A low-complexity read tool with one optional, well-documented parameter and no output schema, so little is strictly required. However, it leaves the core question of whether the returned song is removed from the queue unanswered, which is the behavior an agent most needs to know.
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%, so the single 'channel' parameter is already fully documented with its default resolution rules. The description adds nothing beyond the schema, which is the expected baseline here.
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 clear verb and resource ('Get the next song in the media request queue'), but 'next' is ambiguous against siblings like songrequests_pending, songrequests_queue, and songrequests_playing. The description does not distinguish whether this peeks at the queue head or advances playback, so an agent cannot confidently route between them.
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?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as songrequests_queue or songrequests_pending. The agent must infer selection from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.