Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_finetune

Read-onlyIdempotent

Retrieve a music finetune by finetune_id to check its status, progress, or metadata before using it.

Instructions

Get Music Finetune

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_finetune"
  }
}

Input Schema

NameRequiredDescriptionDefault
finetune_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no mention of auth requirements, retrieval scope, or behavior on a missing/invalid finetune_id.

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

Conciseness3/5

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

It is a single short phrase with no wasted words and is fully front-loaded, but the brevity reflects under-specification rather than tight, information-dense writing. Nothing beyond the bare minimum is conveyed.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining the return value, and it does not. For a retrieval tool with an openWorld hint and one undocumented parameter, an agent learns nothing about what it will get back or what a 'music finetune' is.

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?

Schema description coverage is 0% and the single parameter finetune_id is undocumented in both schema and description. The description does not clarify the expected ID format (e.g., where a finetune_id comes from, as returned by get_finetunes or create_finetune).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get Music Finetune" is essentially a restatement of the tool name with the word "Music" added. It names a verb and resource but gives no detail about what a finetune object contains or how this differs from the sibling get_finetunes (list) tool. This is close to tautology.

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?

There is no statement of when to call this tool versus get_finetunes, create_finetune, update_finetune, or delete_finetune, all of which are close siblings. No prerequisites, no context of use.

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