Skip to main content
Glama
labelgrid

LabelGrid MCP Server

Official

Delete an artist

delete_artist
Destructive

Delete an artist from the catalog only when no releases or tracks reference it. The API refuses deletion if the artist is still associated with any content.

Instructions

Delete an artist. The API refuses deletion when the artist is still referenced by releases or tracks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artist_idYes
Behavior4/5

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

Adds value beyond destructiveHint annotation: explains that deletion refuses when artist is referenced by releases/tracks. This is a critical behavioral caveat.

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

Conciseness5/5

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

Two concise sentences. First states action, second adds key constraint. No wasted 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?

Simple tool, annotations cover destructive hint. Description adds the reference constraint, which is essential. Could note irreversibility, but destructiveHint already implies that.

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

Parameters1/5

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

Schema coverage is 0%, but description provides no additional details about the artist_id parameter (e.g., where to find it). Schema is minimal; description should compensate but doesn't.

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?

States 'Delete an artist' clearly, with specific verb and resource. Distinguishes from other delete tools (e.g., delete_label) by mentioning the artist-specific constraint about references.

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?

Implied usage: delete an artist that is not referenced. No explicit comparison to alternatives like update_artist or when not to use. Missing direct guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/labelgrid/labelgrid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server