Skip to main content
Glama
labelgrid

LabelGrid MCP Server

Official

Create a release (draft)

create_release

Create a new release in draft state by providing required metadata including content type, label, artists, titles, catalog number, artwork AI usage, and primary genre. Use an idempotency key to safely retry the operation.

Instructions

Create a new release in DRAFT state. Pass its metadata in fields. Required: content_type, label_id, artists, titles, cat (catalog number), artwork_ai_usage, primary_genre_id. Pass idempotency_key and reuse the SAME value if you retry a call whose outcome you did not observe — the server deduplicates by it for 24h; without a key each call is a new operation. Add tracks with create_track, then validate_release before distributing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesRelease metadata. Required: content_type, label_id, artists, titles, cat, artwork_ai_usage, primary_genre_id. Many optional fields (dates, copyright lines, genres, per-outlet URLs) are supported — see the API docs.
idempotency_keyNoOptional idempotency key. The server deduplicates by this key for 24h — pass the SAME key when retrying a call whose outcome you did not observe. Without it, each call is a new operation.
Behavior4/5

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

Discloses that creation results in a DRAFT state and explains idempotency deduplication for 24h. No annotations to contradict. Could mention permissions or side effects, but current info is helpful.

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?

Three sentences, each with a distinct purpose: purpose, required fields, idempotency+workflow. Front-loaded and 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?

Covers purpose, required fields, idempotency, and next steps. No output schema, so agents may need to infer return value, but the description is sufficiently complete for a creation tool.

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

Parameters5/5

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

Adds significant value beyond the input schema: lists required sub-fields for 'fields' and explains idempotency_key's role for retries. Schema coverage is 100% and description enriches understanding.

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 release in DRAFT state', specifying the verb (create) and resource (release) with a clear initial status. It also distinguishes from other tools like create_track and validate_release.

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?

Provides clear guidance on required fields, idempotency key usage for retries, and subsequent steps (add tracks with create_track, then validate). Does not explicitly state when not to use this tool, but the workflow context is sufficient.

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