Skip to main content
Glama

List artists

list_artists
Read-onlyIdempotent

Artists by name, with their song counts and a picture Songs belong to an artist; create the artist first. Sorted by name, 50 per page by default: pass q to search by name, and limit/offset to page. image_url is the picture uploaded for it (null without one); while it has none, image_fallback is the cover of its newest song still there that has one (song_id, preview_url 640 px and thumbnail_url 160 px WebP), to show in its place, or null without such a song. It is read-only, never saved as the picture, and follows the newest song (a new song or an archived one changes it).

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_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPart of the artist name
limitNoResults per page, 1-100 (default 50)
offsetNoHow many results to skip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the bar is lower, yet the description adds genuinely non-obvious behavior: name sort order, default page size, nullability of image_url, and the derived image_fallback that tracks the newest extant song with a cover. It also explicitly states the fallback is never saved and that archiving or adding a song changes it, which an agent could not infer from annotations.

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

Conciseness3/5

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

Guidance is front-loaded well, but the second half is one very long run-on sentence with nested parentheticals (dimensions, formats, nullability) that is hard to parse. Meanwhile an unrelated dependency sentence ("create the artist first") occupies scarce space ahead of the pagination rules, so the structure is not optimally ordered.

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?

There is no output schema, so the description must explain return values — and it does, covering song counts, the uploaded picture, and the fallback cover with its resolution variants, plus sort order and paging. For a three-parameter read-only list tool this is close to complete; only explicit sibling routing is absent.

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%, so the schema already carries maxLength, limits, and defaults. The description only restates the same facts at a higher level (q for name search, limit/offset for paging) without adding format or edge-case semantics beyond the schema, so it sits at the baseline.

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 identifies the resource and return payload clearly: artists sorted by name with song counts and a picture. The opening is a fragment with no verb ("Artists by name, with their song counts and a picture"), and the verb only arrives implicitly via the pagination sentence, so it falls short of a crisp verb+resource statement, but an agent can still tell this lists artists rather than songs or characters.

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 gives concrete invocation guidance — pass q to search by name, limit/offset to page, 50 per page by default — which covers the common operating modes. What is missing is any when-to-use-vs-alternative routing (e.g. relative to list_songs when you already know the artist), and the stray sentence "Songs belong to an artist; create the artist first" is a dependency note that reads as misplaced in a read-only list tool and does not clarify when to call this.

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