Skip to main content
Glama

retell_create_conversation_flow

Design structured conversation flows with node-based configurations for AI voice and chat agents.

Instructions

Create a new conversation flow for structured, node-based conversation design.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the conversation flow
nodesNoArray of node configurations defining the flow
edgesNoArray of edge configurations connecting nodes

Implementation Reference

  • Handler case in the executeTool function that proxies the tool call to Retell's /create-conversation-flow API endpoint via POST request with input arguments.
    case "retell_create_conversation_flow":
      return retellRequest("/create-conversation-flow", "POST", args);
  • Input schema for the tool, specifying required 'name' and optional 'nodes' and 'edges' arrays.
    inputSchema: {
      type: "object",
      properties: {
        name: {
          type: "string",
          description: "Name for the conversation flow"
        },
        nodes: {
          type: "array",
          description: "Array of node configurations defining the flow"
        },
        edges: {
          type: "array",
          description: "Array of edge configurations connecting nodes"
        }
      },
      required: ["name"]
    }
  • src/index.ts:804-825 (registration)
    Registration of the tool in the 'tools' array, which is returned by the ListTools handler for MCP tool discovery.
    {
      name: "retell_create_conversation_flow",
      description: "Create a new conversation flow for structured, node-based conversation design.",
      inputSchema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Name for the conversation flow"
          },
          nodes: {
            type: "array",
            description: "Array of node configurations defining the flow"
          },
          edges: {
            type: "array",
            description: "Array of edge configurations connecting nodes"
          }
        },
        required: ["name"]
      }
    },
  • Shared helper function that performs authenticated HTTP requests to the Retell API, used by all tool handlers including this one.
    async function retellRequest(
      endpoint: string,
      method: string = "GET",
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const apiKey = getApiKey();
    
      const headers: Record<string, string> = {
        "Authorization": `Bearer ${apiKey}`,
        "Content-Type": "application/json",
      };
    
      const options: RequestInit = {
        method,
        headers,
      };
    
      if (body && method !== "GET") {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(`${RETELL_API_BASE}${endpoint}`, options);
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(`Retell API error (${response.status}): ${errorText}`);
      }
    
      // Handle 204 No Content
      if (response.status === 204) {
        return { success: true };
      }
    
      return response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral information. It states this is a creation tool (implying mutation/write operation) but doesn't disclose permissions needed, whether the flow is immediately active, rate limits, or what happens on success/failure. The description adds some context about 'structured, node-based design' but lacks critical behavioral details 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.

Conciseness4/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 with no wasted words. It's appropriately sized for a creation tool, though it could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given this is a mutation tool with no annotations and no output schema, the description is minimally adequate but has clear gaps. It covers the basic purpose but lacks behavioral transparency, usage guidelines, and details about the created resource. The 100% schema coverage helps, but for a tool that creates complex conversation flows, more context would be beneficial.

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%, so the schema already documents all three parameters (name, nodes, edges). The description adds no additional parameter semantics beyond what's in the schema—it doesn't explain what 'node configurations' or 'edge configurations' entail, their structure, or examples. Baseline 3 is appropriate when 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 ('Create a new conversation flow') and the resource ('conversation flow'), specifying it's for 'structured, node-based conversation design'. This distinguishes it from general conversation tools but doesn't explicitly differentiate from sibling tools like retell_create_agent or retell_create_chat_agent.

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. The description doesn't mention prerequisites, when this tool is appropriate compared to other creation tools (e.g., retell_create_agent), or any exclusions. Usage context is implied but not explicit.

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/itsanamune/retellsimp'

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