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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_dubbed_metadata

Read-onlyIdempotent

Retrieve metadata for a dubbing project using its dubbing ID. Get status, duration, and details for managing dubbing jobs.

Instructions

Get Dubbing

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": {
      "dubbing_id": "<dubbing_id>"
    },
    "name": "get_dubbed_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
dubbing_idYesID of the dubbing project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond those annotations—it does not say what metadata is returned, whether authentication is required, or any rate limits.

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 description is extremely short but under-specified rather than concise. It lacks the necessary detail to make the tool usable and leaves critical information missing.

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?

Given a simple read-only tool with one documented parameter and annotations covering safety, the description is still incomplete: it does not explain what 'metadata' includes or how this differs from similar dubbing retrieval tools. With no output schema, the description should describe the return value but does not.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter dubbing_id is fully documented in the schema as 'ID of the dubbing project.' The description adds no parameter meaning, but the baseline for high schema coverage with no additional param info is 3.

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?

The description 'Get Dubbing' essentially restates part of the tool name without specifying that it retrieves metadata, and it fails to distinguish this tool from close siblings like get_dubbing_resource, get_dubbed_file, or get_dubbed_transcript_file. The agent cannot tell what resource is actually returned.

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?

No when-to-use guidance is provided, no alternatives are named, and no conditions for selecting this tool over the many other dubbing-related getters are given. The description gives no clue about appropriate context or exclusions.

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