Skip to main content
Glama
projectservan8n

ElevenLabs MCP Server

by projectservan8n
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

check_subscription

Check your ElevenLabs API subscription status to monitor usage and manage your account's current plan details.

Instructions

Check the current subscription status. Could be used to measure the usage of the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • elevenlabs_mcp/server.py:497-502 (handler)
    The check_subscription tool is implemented as a handler function decorated with @mcp.tool, which also serves as its registration in the MCP server. It fetches the user's subscription details from the ElevenLabs API and returns them as formatted JSON text content.
    @mcp.tool(
    description="Check the current subscription status. Could be used to measure the usage of the API."
)
def check_subscription() -> TextContent:
    subscription = client.user.subscription.get()
    return TextContent(type="text", text=f"{subscription.model_dump_json(indent=2)}")

Tool Definition Quality

B3/5.0
Behavior2/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 of behavioral disclosure. It mentions checking subscription status and measuring API usage, but does not disclose critical traits such as whether this requires authentication, rate limits, response format, or potential side effects. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness4/5

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

The description is appropriately sized with two concise sentences that directly address the tool's purpose and a potential use case. It is front-loaded with the core function, and both sentences earn their place by adding value without redundancy. However, it could be slightly more structured by explicitly stating the tool's output or constraints.

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 the lack of annotations and no output schema, the description is incomplete. It does not explain what the subscription status includes (e.g., limits, expiration), how the measurement of API usage is performed, or the return format. For a tool that likely provides critical system information, more context is needed to guide the agent effectively.

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?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description does not need to add parameter semantics, so it meets the baseline for tools with no parameters. No additional parameter information is required or provided.

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 clearly states the tool's purpose as 'Check the current subscription status,' which is a specific verb ('check') and resource ('subscription status'). It distinguishes itself from sibling tools like list_models or get_agent by focusing on subscription status rather than listing or retrieving other resources. However, it does not explicitly differentiate from all siblings, as some might indirectly relate to subscription usage.

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 minimal guidance with 'Could be used to measure the usage of the API,' which implies a context for usage but does not specify when to use this tool versus alternatives or any prerequisites. No explicit when/when-not instructions or named alternatives are provided, leaving the agent with little direction on optimal usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/projectservan8n/elevenlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server