Skip to main content
Glama

get_video_setlist

Read-only

動画IDで配信の情報とセットリスト(タイムスタンプ付きの歌唱一覧)を取得する。

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": {
      "videoId": "<videoId>"
    },
    "name": "get_video_setlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoこのツールを呼ぶ目的やユーザーの依頼の要約(1文・任意)。検索品質の改善のためのログに記録されます
videoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by saying the response contains both stream metadata and a timestamped song list, which the annotations do not convey and there is no output schema to fall back on. It does not say what happens for an unknown ID or a video with no setlist.

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?

One sentence, front-loaded with the lookup key and followed by the two things returned. Nothing is redundant, though the extreme brevity leaves no room for the qualifications noted above.

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 two-parameter read-only lookup with no output schema, the description covers the input key and the shape of the return value (stream info plus timestamped setlist), which is the main thing an agent needs. Missing edge-case behavior around missing setlists or invalid IDs is a minor gap rather than a blocker.

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 coverage is 50%: the context parameter is documented in the schema, while videoId has no description there. The phrase 動画IDで partially compensates by confirming videoId identifies the stream itself, but the description never mentions the optional context logging parameter or what qualifies as a valid video ID.

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?

The description states a specific verb (取得する) and two concrete resources (配信の情報 and セットリスト), scoped by 動画ID. That is enough to separate it from siblings like get_singer or get_song, which return different entities. It stops short of naming an alternative, so it is clear but not maximally differentiated.

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?

Usage is only implied: the agent must infer that this tool applies when it already holds a video ID for a stream. There is no statement about when to prefer it over search or fetch, and no exclusions such as non-stream videos or videos without setlists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources