Skip to main content
Glama
Sign In
ytm-runlist-mcp

ytm-runlist-mcp

by gittgi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_playlist_tracks_tool

Retrieve tracks from a YouTube Music playlist, including playlist_item_id for reordering.

Instructions

Return tracks from a playlist, including playlist_item_id needed for reordering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist_tracks_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlist_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only mentions returning tracks and a specific field, but omits details on authentication, rate limits, pagination, error handling, or the structure of the output beyond the one field.

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

Conciseness4/5

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

The description is a single, focused sentence that efficiently conveys the core purpose. While concise, it could be slightly expanded to include parameter details without losing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 param, output schema exists), the description should cover basic usage and output. It lacks explanation of the output format, error handling, and fails to compensate for absent annotations, making it incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must explain parameters. It does not describe the playlist_id parameter at all (no format, source, or validation hints), leaving the agent with only the schema type and name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns tracks from a playlist, highlighting the inclusion of playlist_item_id for reordering, which distinguishes it from sibling tools focused on reordering operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly guides usage by noting the relevance of playlist_item_id for reordering, suggesting this tool is a prerequisite before reordering. It lacks explicit when-not-to-use or alternative names, but the context is clear enough.

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