Skip to main content
Glama

delete_conversation

Permanently remove a conversation from the Tavus MCP Server using its unique identifier to manage video generation and AI interactions.

Instructions

Delete a conversation permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_idYesUnique identifier for the conversation

Implementation Reference

  • The deleteConversation method is the handler that executes the delete_conversation tool logic. It extracts conversation_id from args, makes a DELETE request to /conversations/{conversation_id}, and returns a success message.
    private async deleteConversation(args: any) {
      const { conversation_id } = args;
      await this.axiosInstance.delete(`/conversations/${conversation_id}`);
      return {
        content: [{
          type: 'text',
          text: `Successfully deleted conversation ${conversation_id}`,
        }],
      };
    }
  • src/index.ts:428-441 (registration)
    Registration of the delete_conversation tool with its name, description, and inputSchema defining the required conversation_id parameter.
    {
      name: 'delete_conversation',
      description: 'Delete a conversation permanently',
      inputSchema: {
        type: 'object',
        properties: {
          conversation_id: {
            type: 'string',
            description: 'Unique identifier for the conversation',
          },
        },
        required: ['conversation_id'],
      },
    },
  • Switch case routing that maps the 'delete_conversation' tool name to the deleteConversation handler method.
    case 'delete_conversation':
      return await this.deleteConversation(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 full burden for behavioral disclosure. It mentions 'permanently' which indicates irreversibility, but lacks critical details like required permissions, confirmation prompts, side effects on related data, error conditions, or what happens after deletion. For a destructive operation, this leaves significant behavioral gaps.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple deletion operation and front-loads the essential information without unnecessary elaboration.

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 insufficient. It doesn't explain what 'permanently' entails operationally, what verification occurs, whether deletion cascades to related resources, or what response to expect. Given the high-stakes nature of deletion and lack of structured safety indicators, more behavioral context is needed.

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?

With 100% schema description coverage and only one parameter, the schema already fully documents the conversation_id parameter. The description doesn't add parameter-specific information beyond what's in the schema, but with minimal parameters and complete schema coverage, a baseline of 4 is appropriate as the description doesn't need to compensate for schema gaps.

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 conversation') with the qualifier 'permanently' indicating irreversible removal. It distinguishes from sibling 'end_conversation' by specifying deletion rather than termination, but doesn't explicitly contrast with other delete_* tools for different resource types.

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 like 'end_conversation' or other deletion tools for different resources. The description doesn't mention prerequisites, recovery options, or contextual constraints for choosing this destructive operation.

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