channels_getRetrieves public details of a StreamElements channel using its ID or name. Provide a channel name or 24-character hex ID to fetch profile info; defaults to your own channel.
Get public details of a StreamElements channel by channel id or channel name.
| Name | Required | Description | Default |
|---|---|---|---|
| channel | No | Channel id (24-char hex) or channel name. Defaults to your channel. |
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 the safety profile is covered. The description adds the useful qualifier that only 'public' details are returned, hinting at a visibility restriction, but says nothing about return shape or rate limits.
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 efficient sentence with the verb, resource, and identifiers front-loaded. No filler, though it could be slightly more informative at the same length.
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 tool with full schema coverage, the description is adequate but thin: it does not clarify what 'public details' includes or how it differs from channels_get_details. No output schema exists, so some return-value context would have helped.
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 (id, name, defaults to your channel) is already fully documented in the schema. The description restates id-or-name but adds no format or default semantics beyond it.
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 (Get) and resource (StreamElements channel) plus the accepted identifiers. The 'public details' qualifier hints at scope, but it does not clearly differentiate from siblings channels_get_details or channels_me, which an agent would have to resolve on its own.
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 mention of when to prefer channels_me or channels_get_details, and no prerequisites. Usage is only implied by the description text.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.