Skip to main content
Glama

create_conversation

Start a conversational video interface using AI replicas and personas to enable interactive video conversations with custom context and recording options.

Instructions

Create a new conversational video interface

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
replica_idNoReplica to use for the conversation
persona_idNoPersona to use for the conversation
conversation_nameNoName for the conversation
callback_urlNoURL to receive conversation events
conversational_contextNoContext for the conversation
custom_greetingNoCustom greeting message
enable_recordingNoEnable conversation recording

Implementation Reference

  • The createConversation handler method that executes the tool logic. It makes a POST request to the Tavus API /conversations endpoint with the provided arguments and returns the response data in MCP format.
    private async createConversation(args: any) {
      const response = await this.axiosInstance.post('/conversations', args);
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2),
        }],
      };
    }
  • The input schema definition for the create_conversation tool. Defines all input parameters including replica_id, persona_id, conversation_name, callback_url, conversational_context, custom_greeting, and enable_recording with their types and descriptions.
    {
      name: 'create_conversation',
      description: 'Create a new conversational video interface',
      inputSchema: {
        type: 'object',
        properties: {
          replica_id: {
            type: 'string',
            description: 'Replica to use for the conversation',
          },
          persona_id: {
            type: 'string',
            description: 'Persona to use for the conversation',
          },
          conversation_name: {
            type: 'string',
            description: 'Name for the conversation',
          },
          callback_url: {
            type: 'string',
            description: 'URL to receive conversation events',
          },
          conversational_context: {
            type: 'string',
            description: 'Context for the conversation',
          },
          custom_greeting: {
            type: 'string',
            description: 'Custom greeting message',
          },
          enable_recording: {
            type: 'boolean',
            description: 'Enable conversation recording',
          },
        },
      },
    },
  • src/index.ts:355-391 (registration)
    The tool registration for create_conversation in the ListToolsRequestSchema handler. Registers the tool name, description, and inputSchema as part of the available tools list.
    {
      name: 'create_conversation',
      description: 'Create a new conversational video interface',
      inputSchema: {
        type: 'object',
        properties: {
          replica_id: {
            type: 'string',
            description: 'Replica to use for the conversation',
          },
          persona_id: {
            type: 'string',
            description: 'Persona to use for the conversation',
          },
          conversation_name: {
            type: 'string',
            description: 'Name for the conversation',
          },
          callback_url: {
            type: 'string',
            description: 'URL to receive conversation events',
          },
          conversational_context: {
            type: 'string',
            description: 'Context for the conversation',
          },
          custom_greeting: {
            type: 'string',
            description: 'Custom greeting message',
          },
          enable_recording: {
            type: 'boolean',
            description: 'Enable conversation recording',
          },
        },
      },
    },
  • The switch case routing for the create_conversation tool in the CallToolRequestSchema handler. Routes incoming tool calls to the createConversation method with the request arguments.
    case 'create_conversation':
      return await this.createConversation(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. While 'create' implies a write operation, the description doesn't address important behavioral aspects like required permissions, whether this operation is idempotent, what happens on failure, or what the typical response looks like. For a creation tool with 7 parameters and no annotations, this is insufficient.

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 gets straight to the point. There's no wasted language or unnecessary elaboration. It's appropriately sized for a tool description.

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 complexity of a creation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after creation, what the expected response looks like, or provide any context about the conversational video interface being created. The description should do more to compensate for the lack of structured metadata.

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 schema description coverage is 100%, so all parameters are documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('create') and resource ('conversational video interface'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'create_lipsync', 'create_persona', or 'create_replica', which all create different resources in the same domain.

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. There are multiple sibling tools for creating different resources (lipsync, persona, replica), but the description doesn't indicate when a conversational video interface is needed versus those other resources.

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