Skip to main content
Glama
MCPGeneration-for-ElevenLabs

MCPGeneration-for-ElevenLabs

update_music_finetune

Update a music finetune's metadata—name, tags, visibility, and primary genre—by finetune ID to keep documented details accurate and organized.

Instructions

Update documented metadata fields for a music finetune. The optional module is disabled by default.

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": {
      "finetune_id": "<finetune_id>"
    },
    "name": "update_music_finetune"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
tagsNo
visibilityNo
finetune_idYes
primary_genreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure for a mutation tool. It does not explain whether updates are partial or full, what happens to omitted fields, what permissions are required, whether changes are reversible, or what errors may occur. The optional module sentence is unexplained and adds no actionable behavioral context.

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

Conciseness2/5

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

The first sentence is front-loaded and to the point, but the second sentence is confusing and does not appear to help an agent call the tool correctly. With only two sentences total, the irrelevant or ambiguous module note materially reduces structural quality.

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

Completeness1/5

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

This is a mutation tool with five parameters, zero schema description coverage, no annotations, and no output schema. The description does not cover essential operational details such as partial-update semantics, field meanings, permissions, or expected results. It is far too thin for the tool's complexity.

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 description coverage is 0%, so the description must compensate for five undocumented parameters. It does not name or explain any of the parameters (name, tags, visibility, primary_genre, or finetune_id) or their formats and constraints. Saying 'metadata fields' generically provides no meaning beyond the bare schema.

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?

The description states a specific verb and resource: update documented metadata fields for a music finetune. This distinguishes it from siblings like get_music_finetune, list_music_finetunes, delete_music_finetune, and create_music_finetune. However, 'documented metadata fields' is somewhat vague, and the second sentence about the optional module is ambiguous.

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?

The description provides no when-to-use guidance, no comparison with sibling tools, and no prerequisites such as requiring an existing finetune ID. The note that 'the optional module is disabled by default' does not clarify when this tool should be selected or avoided.

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

Deploy Server

Other Tools