Skip to main content
Glama

Create an artist

create_artist

Add an artist by name Names are unique per organization (409 when taken). An artist workspace holds one artist: a second one is refused (409) until the workspace becomes a label (update_organization). Works without a plan, so onboarding can add the artist first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe artist name
catalog_artist_idNo
catalog_confirmedNoSet true after the user confirms they manage the selected artist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / catalog_artist_id
      Added value: +{
      +  "pattern": "^\\d{1,15}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / catalog_confirmed
      Added value: +{
      +  "description": "Set true after the user confirms they manage the selected artist",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: 409 on duplicate name, 409 on a second artist in a workspace, and the fact that it works without a plan so onboarding can proceed. Annotations already cover the safety profile (destructiveHint=false, openWorldHint=false), so this extra detail is a genuine contribution rather than a necessity.

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?

Three tight sentences, front-loaded with the core action and then the failure modes. Minor flaw: the first sentence runs into the second without punctuation ("by name Names are unique"), slightly hurting readability but not wasting words.

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?

Adequate for a 3-parameter mutation with no output schema: error conditions and plan requirements are covered. It falls short on the catalog-identification flow, which is the least self-evident part of the call and the most likely place an agent goes wrong.

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

Parameters2/5

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

The description explains only the name parameter ("by name"), which the schema already documents at maxLength 200. catalog_artist_id has no description in schema or prose, and the catalog_confirmed workflow (implying a prior find_artist_in_catalog confirmation step) is never explained, leaving a third of the parameters opaque.

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: "Add an artist by name." It is clearly distinct from rename_artist or archive_artist, though it never names a sibling tool to contrast with, so the differentiation is left implicit.

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 strong preconditions (unique per organization, one artist per workspace, no plan required) and points to update_organization for the label conversion path. However, it never says when to use this versus link_artist or find_artist_in_catalog, which is exactly the ambiguity an agent faces with catalog_artist_id in the schema.

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