Skip to main content
Glama

delete_persona

Remove a persona permanently from the Tavus MCP Server to manage AI video generation and conversational AI resources.

Instructions

Delete a persona permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
persona_idYesUnique identifier for the persona

Implementation Reference

  • The deletePersona handler method that executes the tool logic - takes a persona_id argument, makes a DELETE request to the API endpoint /personas/{persona_id}, and returns a success message
    private async deletePersona(args: any) {
      const { persona_id } = args;
      await this.axiosInstance.delete(`/personas/${persona_id}`);
      return {
        content: [{
          type: 'text',
          text: `Successfully deleted persona ${persona_id}`,
        }],
      };
    }
  • src/index.ts:528-541 (registration)
    Tool registration defining 'delete_persona' with description 'Delete a persona permanently' and inputSchema specifying persona_id as a required string parameter
    {
      name: 'delete_persona',
      description: 'Delete a persona permanently',
      inputSchema: {
        type: 'object',
        properties: {
          persona_id: {
            type: 'string',
            description: 'Unique identifier for the persona',
          },
        },
        required: ['persona_id'],
      },
    },
  • Switch case handler that routes 'delete_persona' tool calls to the deletePersona method with request arguments
    case 'delete_persona':
      return await this.deletePersona(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 permanent, which is crucial for a destructive operation, but lacks details on permissions required, error conditions (e.g., invalid persona_id), side effects, or confirmation prompts. This is a significant gap for a mutation tool.

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, direct sentence with zero waste—'Delete a persona permanently'—front-loading the key action and critical detail (permanence) efficiently.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks essential context such as what 'permanently' entails (e.g., irreversible, no recovery), potential impacts, or response format, leaving the agent under-informed for safe use.

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 'persona_id' fully documented in the schema. The description adds no additional parameter details beyond implying persona_id is needed, so it meets the baseline of 3 where the schema does 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 persona'), and specifies the permanence ('permanently'), which distinguishes it from potential soft-delete operations. However, it doesn't explicitly differentiate from sibling tools like delete_conversation or delete_replica, which follow the same pattern.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a persona_id from get_persona or list_personas), exclusions, or comparisons with related tools like patch_persona for updates.

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