Skip to main content
Glama

List song imports

list_song_imports
Read-onlyIdempotent

Released songs being imported, failed ones waiting for a file, and today’s done ones Newest first. status: queued, fetching, done (song_id: the song made) or failed (error says why; add_song_import_audio with the file, or cancel_song_import).

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

Input Schema

NameRequiredDescriptionDefault
statusNoOnly imports with this status
artist_idNoOnly this artist’s imports

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish safe read-only, idempotent, closed-world behavior. The description adds genuine context beyond that: it defines the status lifecycle, says results are newest-first, and notes a failed import carries an error explaining why. It leaves the returned field set and any result limits unspecified.

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?

Two dense sentences with no filler, and the scope and ordering come first. The wording is clipped ('today's done ones Newest first') and missing punctuation, which slightly hurts readability but wastes no space.

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

Completeness3/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 carries the burden of explaining return values, and it only partially does so: it names song_id and error but not the full record shape, result limits, or pagination. For a simple two-parameter read it is close to adequate, but the return-format gap is real.

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

Parameters4/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 both parameters. The description still adds meaning by expanding the status enum into lifecycle states (queued, fetching, done, failed) and explaining what done and failed results contain. The artist_id filter is never mentioned, but the schema handles it.

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 defines the resource precisely: imports of released songs, split into active, failed, and today's completed ones, ordered newest first. That distinguishes it from siblings like list_released_songs and get_song_import. The opening fragment is telegraphic rather than a clean verb+resource statement, which keeps it just below the top mark.

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

Usage Guidelines4/5

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

It routes the agent to the right follow-up tools by state: failures mean either add_song_import_audio with the file or cancel_song_import. It also implies scope boundaries by saying only today's done imports appear. It does not explicitly say when to use get_song_import instead, so it stops short of 5.

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