Skip to main content
Glama
MCPGeneration-for-ElevenLabs

MCPGeneration-for-ElevenLabs

get_music_finetune

Retrieve metadata for a specific music finetune by ID, enabling inspection of finetune details when the optional finetune module is enabled.

Instructions

Get metadata for one music finetune. The optional finetune 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": "get_music_finetune"
  }
}

Input Schema

NameRequiredDescriptionDefault
finetune_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds one genuinely useful disclosure, the module-disabled-by-default prerequisite, but says nothing about permissions, error behaviour when the module is off, or the shape of the returned metadata. For a read with no annotation coverage, this is a real but partial contribution.

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?

Two short sentences, zero waste, with the tool's purpose front-loaded ahead of the availability caveat. Nothing is padded or repeated.

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?

For a simple single-parameter lookup, the description covers the purpose and the module-disabled prerequisite. Because there is no output schema, it should at least sketch what 'metadata' includes, and it should say how to obtain a valid finetune_id. Those gaps keep it at minimally adequate.

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 schema has one required parameter, finetune_id, at 0% description coverage, so the schema supplies only a type and length bounds. The description implies the id addresses 'one music finetune' but never states the expected id format or where the id comes from, for example list_music_finetunes or create_music_finetune.

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 names a specific verb and resource: 'Get metadata for one music finetune'. This clearly separates it from list_music_finetunes, update_music_finetune, and delete_music_finetune, though those siblings are never named. An agent can infer the difference from the verb and the singular scope.

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?

The second sentence states that the optional finetune module is disabled by default, which is a real precondition for calling the tool. However, it never says when to use this tool rather than list_music_finetunes or get_music_finetune's other siblings, and it gives no guidance on what to do if the module is disabled.

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