Skip to main content
Glama

delete_speech

Remove a speech permanently from the Tavus MCP Server using its unique identifier to manage synthesized audio content.

Instructions

Delete a speech permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speech_idYesUnique identifier for the speech

Implementation Reference

  • The deleteSpeech handler method that executes the tool logic - makes a DELETE request to the API endpoint /speech/{speech_id} and returns a success message
    private async deleteSpeech(args: any) {
      const { speech_id } = args;
      await this.axiosInstance.delete(`/speech/${speech_id}`);
      return {
        content: [{
          type: 'text',
          text: `Successfully deleted speech ${speech_id}`,
        }],
      };
    }
  • Tool schema definition with name, description, and inputSchema specifying speech_id as a required string parameter
    {
      name: 'delete_speech',
      description: 'Delete a speech permanently',
      inputSchema: {
        type: 'object',
        properties: {
          speech_id: {
            type: 'string',
            description: 'Unique identifier for the speech',
          },
        },
        required: ['speech_id'],
      },
    },
  • src/index.ts:756-757 (registration)
    Switch case routing that maps 'delete_speech' tool calls to the deleteSpeech handler method
    case 'delete_speech':
      return await this.deleteSpeech(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is 'permanently' destructive, which is useful, but lacks details on permissions, error handling (e.g., what happens if speech_id is invalid), or side effects. This is a significant gap for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence with no wasted words, clearly front-loading the key action and resource. Every word earns its place by specifying the permanence of the deletion.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks crucial context such as confirmation of deletion, return values, error conditions, or dependencies on other tools (e.g., get_speech). This leaves gaps that could hinder an AI agent's correct invocation.

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%, with the single parameter 'speech_id' documented as a unique identifier. The description does not add any meaning beyond this, such as format examples or sourcing instructions, so it meets the baseline of 3 where the schema handles the heavy lifting.

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 action ('Delete') and resource ('a speech'), with 'permanently' adding specificity about the nature of the deletion. However, it does not explicitly differentiate from sibling tools like delete_conversation or delete_video, which have similar structures but target different resources.

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 guidance is provided on when to use this tool versus alternatives. For example, it does not mention prerequisites (e.g., needing the speech_id from get_speech or list_speeches), nor does it clarify if it's irreversible or suggest when to use rename_speech instead for non-destructive changes.

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/rakeshdavid/Tavus-MCP'

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