Skip to main content
Glama

List songs

list_songs
Read-onlyIdempotent

Songs with their cover, duration and analysis status A song must be analyzed (analysis.status "ready") before videos can be made. 50 per page by default: pass q to search, and limit/offset to page. cover_art.url is the cover at up to 1536 px (JPEG; width and height describe it), preview_url a 640 px and thumbnail_url a 160 px WebP; cover_art is null for a song without cover art (it is optional). Image links are signed for 7 days and stay the same all day, so they can be cached.

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

Input Schema

NameRequiredDescriptionDefault
qNoPart of the song title or artist name
sortNotitle (default): by artist then title; newest: latest uploads first
limitNoResults per page, 1-100 (default 50)
offsetNoHow many results to skip
statusNoOnly songs whose analysis has this status (ready = usable for videos)
artist_idNoOnly this artist’s songs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the bar is lower, and the description adds real context beyond them: 50-per-page default, cover_art being null when absent, three image sizes with formats, and signed URLs valid for 7 days and stable within a day (cacheable). It stops short of auth, rate-limit or pagination-boundary details.

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?

Content is front-loaded with what is returned, then paging and image URL details, and every sentence carries useful information. The prose is dense and mixes return-value documentation into a single run-on block, which slightly hurts scanability but wastes no words.

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?

With no output schema, the description correctly carries the return-value burden: it explains cover, duration, analysis status, the three cover_art URL variants and their nullability, plus paging behavior. Only minor gaps remain, such as whether a total count is returned.

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 100%, so the schema already documents every parameter including sort defaults and status enum meaning. The description mainly restates the 50-per-page default and the q/limit/offset purpose rather than adding new meaning or format hints beyond the schema.

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 names the resource and the returned fields (cover, duration, analysis status) and implies listing with paging/search, but the verb itself is only carried by the tool name/title, and it does not distinguish itself from siblings like show_songs or list_song_covers.

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?

It offers implied usage: pass q to search, limit/offset to page, and notes that a song must be analyzed (status "ready") before videos can be made. There is no explicit when-to-use versus an alternative tool and no statement of exclusions or prerequisites in terms of tool choice.

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