Skip to main content
Glama

Get fallback playlist

songrequests_playlist
Read-only

Retrieve the songs in a StreamElements channel's playlist that plays when the request queue is empty, so you can review or manage the fallback queue.

Instructions

Get the songs on the channel's playlist, which plays when the request queue is empty.

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": "songrequests_playlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage token: the nextPage value from the previous response
limitNoItems per page
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

Does 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 genuine context that this is the fallback content played when the queue is empty, but says nothing about pagination behavior or result volume even though page/limit parameters exist.

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

Conciseness5/5

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

A single front-loaded sentence with the resource first and the behavioral qualifier second. No filler, nothing redundant.

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?

For a read-only list tool with no output schema and fully documented parameters, the description is nearly sufficient. The only omission is any mention of pagination or the fact that results are paged, which the schema implies but the description never states.

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%, with page, limit, and channel all documented in the schema, including defaults and constraints. The description adds no parameter meaning beyond that, so the baseline 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?

States a specific verb and resource ('Get the songs on the channel's playlist') and adds a distinguishing scope note ('plays when the request queue is empty') that separates it from siblings like songrequests_queue and songrequests_pending. It doesn't name those siblings explicitly, so it stops short of a 5.

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?

The clause 'which plays when the request queue is empty' implies the tool's role (inspecting fallback content), but there is no explicit when-to-use statement, no exclusions, and no named alternative such as songrequests_queue. Usage is left to inference.

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

Deploy Server

Other Tools