Skip to main content
Glama

List Looks

list_looks
Read-onlyIdempotent

Browse Official, Community and your own Looks A Look is a complete, reusable lyric-video design. Pass its id as {"mode":"existing","id":…} to reuse it exactly. A Look that shows an artist (featured_artist) is private and only serves that artist's songs: choosing for a song, pass its artist_id to leave out Looks that show another artist.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch words
sortNo
limitNo
scopeNoWhich library; default all
offsetNo
categoryNoA category id from get_options
artist_idNoThe artist of the song you are choosing for: Looks that show another artist are left out
lyric_styleNoA lyric style id from get_options (how the lyrics move)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / artist_id
      Added value: +{
      +  "description": "The artist of the song you are choosing for: Looks that show another artist are left out",
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / lyric_style
      Added value: +{
      +  "description": "A lyric style id from get_options (how the lyrics move)",
      +  "maxLength": 40,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context beyond them: Looks featuring an artist are private and only serve that artist's songs, and artist_id filters those out. It also explains the downstream consumption pattern of the returned id ({mode:'existing', id:…}), which is useful non-obvious behavior. Pagination/return shape is not mentioned.

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?

Purpose is front-loaded, which is good, but the text is a run-on: the first sentence is missing a period before 'A Look', and the final clause ('choosing for a song, pass its artist_id...') is grammatically tangled enough to require a reread. Content earns its place, but the structure works against fast parsing.

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 still tells the agent what it gets back (Looks with ids) and how to reuse one, and it covers the non-obvious privacy rule that governs which Looks are even eligible. For an 8-param read-only browse tool with full annotation coverage, nothing essential is missing.

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 63%, and the description reinforces the two most consequential semantics: the scope taxonomy (official/community/mine) and artist_id exclusion behavior. The other parameters (q, sort, limit, offset, category, lyric_style) get nothing beyond the schema, and several are undocumented in both places, so the description only partially compensates.

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?

States a specific verb and resource ('Browse Official, Community and your own Looks') and defines what a Look is ('a complete, reusable lyric-video design'), which an agent cannot infer from the name alone. It does not explicitly distinguish itself from the close siblings get_look and show_looks, so the differentiation is partial.

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?

Gives one concrete conditional: when choosing a Look for a song, pass that song's artist_id to exclude Looks showing another artist. However, it never says when to use list_looks versus get_look or show_looks, nor when to prefer scope=official/community/mine, leaving the primary routing decision to inference.

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