Skip to main content
Glama

Fill in the artist's profile

update_profile
Destructive

Set artist details: name, country, genre, tone, description, main markets, Promo's post language, the three bios and links. Send only the fields you are changing. Call get_requirements first for the exact limits. An over-long value is refused with the number it got.

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": {
      "fields": "<fields>"
    },
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
fieldsYesThe fields to set, by the `name` get_requirements gives each one.
dry_runNoTrue to see what would change, and what it would replace, without writing anything. Use it before overwriting words the artist wrote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the destructiveHint and idempotentHint=false annotations, the description discloses that over-long values are rejected with the offending count, and that partial field submission is the intended merge semantics rather than whole-object replacement. It stops short of warning about overwriting artist-written text in the body itself, though the dry_run schema parameter does carry that guidance.

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, front-loaded with the settable fields, then the partial-update rule, then the prerequisite and the failure mode. No filler and no repetition of the schema.

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?

For a destructive nested-object mutation with arbitrary field keys, the description correctly delegates field enumeration and limits to get_requirements and states the rejection behavior. It does not say what a successful call returns, but no output schema exists so that gap is minor relative to the write semantics it does cover.

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 baseline would be 3, but the description adds real meaning: the keys inside the `fields` object must match whatever names get_requirements returns, and unspecified fields are left alone. That is a semantic contract the free-form additionalProperties object does not express on its own.

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?

A specific verb ("Set") plus resource (artist details) and an enumerated list of settable fields, so the agent knows exactly what this writes. It does not differentiate itself from the nearby profile tools (get_profile, propose_profile), so the agent must infer read-only, draft, and direct-write roles from the names alone.

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?

Clear operational context is given: send only changed fields, and call get_requirements first for exact limits. There is no when-not-to-use guidance, notably no hint about preferring propose_profile over a direct write, but the partial-update and prerequisite instructions are concrete and actionable.

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