Skip to main content
Glama

delete_replica

Permanently remove a video replica by its unique identifier to manage storage and resources in the Tavus MCP Server.

Instructions

Delete a replica permanently

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
replica_idYesUnique identifier for the replica

Implementation Reference

  • The deleteReplica handler method that executes the tool logic. It extracts replica_id from args, makes a DELETE request to /replicas/{replica_id} endpoint, and returns a success message.
    private async deleteReplica(args: any) {
      const { replica_id } = args;
      await this.axiosInstance.delete(`/replicas/${replica_id}`);
      return {
        content: [{
          type: 'text',
          text: `Successfully deleted replica ${replica_id}`,
        }],
      };
    }
  • Input schema definition for delete_replica tool. Defines a required 'replica_id' property of type string with description 'Unique identifier for the replica'.
    inputSchema: {
      type: 'object',
      properties: {
        replica_id: {
          type: 'string',
          description: 'Unique identifier for the replica',
        },
      },
      required: ['replica_id'],
    },
  • src/index.ts:200-213 (registration)
    Tool registration for delete_replica. Registers the tool with name 'delete_replica', description 'Delete a replica permanently', and the input schema.
    {
      name: 'delete_replica',
      description: 'Delete a replica permanently',
      inputSchema: {
        type: 'object',
        properties: {
          replica_id: {
            type: 'string',
            description: 'Unique identifier for the replica',
          },
        },
        required: ['replica_id'],
      },
    },
  • Switch case that dispatches delete_replica tool calls to the deleteReplica handler method, passing the request arguments.
    case 'delete_replica':
      return await this.deleteReplica(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 states the action is permanent ('permanently'), which is useful, but lacks critical details: whether authentication is required, if deletion is reversible, what happens to associated data, or error conditions. For a destructive operation, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise at just three words, front-loading the key action ('Delete') and qualification ('permanently') with zero wasted language. Every word earns its place, making it easy to parse quickly.

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 doesn't explain what a 'replica' is in this context, what the deletion entails, or what the response looks like (e.g., success confirmation or error). Given the complexity of permanent deletion, more context is needed for safe and effective 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?

The input schema has 100% description coverage, with replica_id clearly documented as a 'Unique identifier for the replica.' The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score 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 target resource ('a replica'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other delete operations like delete_conversation or delete_persona, which would require mentioning what distinguishes a replica from other 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., replica must exist), exclusions (e.g., cannot delete active replicas), or relationships with sibling tools like create_replica or rename_replica, leaving the agent with insufficient context for appropriate selection.

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