Skip to main content
Glama
labelgrid

LabelGrid MCP Server

Official

Create an artist

create_artist

Create a new artist by providing required attributes such as artist name, and optional fields like full name, location, and platform URLs.

Instructions

Create a new artist. Pass its attributes in fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesArtist attributes. Required: artist_name (string). Common optional: full_name, email, location, bio_short, bio_full, isni, default_language, and platform profile URLs (spotify_url, applemusic_url, youtube_url, etc.). See the API docs for the full field list.
Behavior2/5

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

Annotations lack readOnlyHint or destructiveHint, so description carries full burden. Only states 'Create a new artist' without disclosing mutation behavior, idempotency, or response format.

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?

Extremely concise: one sentence with no wasted words. Appropriately sized for a simple creation tool.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks output schema and annotations. The description provides no information about success outcomes, errors, or API references. Incomplete for a creation tool with nested parameters.

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% with detailed field descriptions. The description adds minimal value ('Pass its attributes in `fields`'), so baseline 3 is appropriate.

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?

The description clearly states 'Create a new artist' with a specific verb and resource. Among sibling tools (e.g., create_publisher, create_release), it unambiguously distinguishes itself.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., update_artist) or prerequisites. Implicit from tool name, but no explicit context.

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