Skip to main content
Glama

list_singer_performances

Read-only

1人の歌い手の歌唱パフォーマンスを新しい順に全件たどる(一括取得用・ページング対応)。1ページ最大50件。全件取得するときは limit: 50 を指定して呼び出し回数を減らすこと。totalCount に条件に合致する全件数、hasMore に次ページの有無が入るので、offset を limit ずつ進めれば全件を取得できる。同一の歌枠内の並びはセットリスト順ではない(セットリスト順は get_video_setlist を使う)。singerId は search_singers / get_singer で得たIDを渡す。since/until で期間を絞れる(未指定なら全期間)。日時は ISO 8601 形式のみ(例: 2026-07-01 / 2026-07-01T12:00:00+09:00)。タイムゾーンオフセットのない日時は日本時間(JST)として解釈される。YYYY-MM-DD は since ではその日の JST 0時、until ではその日の終わり(当日を含む)として解釈される。「この歌い手が歌った曲を全部知りたい」「レパートリー全体を分析したい」に答える用途。直近の動向を見るだけなら recent_streams を使う。

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": {
      "singerId": "<singerId>"
    },
    "name": "list_singer_performances"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, destructiveHint=false, openWorldHint=false; the description goes far beyond by disclosing pagination behavior (max 50 per page, how to loop with offset), the response contract (totalCount = total matches, hasMore = next page exists), sort ordering (newest first), and an ordering caveat that items within one video are not in setlist order. Nothing about the tool's runtime behavior is left implicit.

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 purpose and scope are front-loaded, followed by pagination mechanics, ordering caveat, prerequisites, date semantics, and the alternative tool — a logical progression with no filler sentences. Minor duplication: '1ページ最大50件' restates the schema's maximum: 50, and the timezone rules are dense enough to slow scanning, but overall the length is justified by the tool's complexity.

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

Completeness5/5

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

With no output schema, the description supplies the relevant response fields (totalCount, hasMore) and the pagination loop needed to consume them. For a 6-parameter, paginated read tool, an agent has everything required to call it correctly, including date-format and timezone pitfalls.

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

Parameters5/5

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

Schema coverage is only 17% (only the self-describing 'context' field), so the description must carry the burden and does: it defines limit's practical value (50), offset's stepping semantics, singerId's provenance, and a detailed since/until contract including ISO 8601-only format, JST assumption for offset-less timestamps, and date-only boundary semantics (start-of-day for since, end-of-day inclusive for until). This is meaning well beyond what the schema types convey.

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 first sentence names a specific verb and resource (traverse all singing performances of one singer, newest first) plus the retrieval mode (bulk, paginated). It explicitly distinguishes itself from get_video_setlist (setlist ordering) and recent_streams (recent trends only), so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

It states when to use this tool ('want every song this singer has sung', 'analyze the whole repertoire') and when not to ('if you only want recent trends, use recent_streams'), and gives a concrete prerequisite: obtain singerId via search_singers / get_singer. It even prescribes a calling pattern (limit: 50, advance offset by limit) to reduce round trips.

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