Skip to main content
Glama

retell_update_conversation_flow

Modify conversation flows by updating nodes and edges to adjust AI agent behavior and call handling logic.

Instructions

Update a conversation flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_flow_idYesThe conversation flow ID to update
nameNoNew name
nodesNoUpdated nodes
edgesNoUpdated edges

Implementation Reference

  • The execution handler for the retell_update_conversation_flow tool. It extracts the conversation_flow_id from input arguments and forwards the remaining data as a PATCH request to the Retell API endpoint `/update-conversation-flow/{conversation_flow_id}` using the shared retellRequest utility.
    case "retell_update_conversation_flow": {
      const { conversation_flow_id, ...flowUpdateData } = args;
      return retellRequest(`/update-conversation-flow/${conversation_flow_id}`, "PATCH", flowUpdateData as Record<string, unknown>);
    }
  • The tool schema registration, defining the name, description, and input schema (including required conversation_flow_id and optional name, nodes, edges) used for validation and tool listing.
    {
      name: "retell_update_conversation_flow",
      description: "Update a conversation flow.",
      inputSchema: {
        type: "object",
        properties: {
          conversation_flow_id: {
            type: "string",
            description: "The conversation flow ID to update"
          },
          name: {
            type: "string",
            description: "New name"
          },
          nodes: {
            type: "array",
            description: "Updated nodes"
          },
          edges: {
            type: "array",
            description: "Updated edges"
          }
        },
        required: ["conversation_flow_id"]
      }
    },
  • src/index.ts:1283-1285 (registration)
    The general tool registration handler that returns the full tools array (including this tool's schema) in response to ListTools requests.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:1287-1293 (registration)
    The tool execution request handler registration, which dispatches to executeTool based on tool name, handling the call for retell_update_conversation_flow via the switch case.
    // Register tool execution handler
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeTool(name, args as Record<string, unknown>);
        return {
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Update' which implies a mutation, but lacks details on permissions required, whether updates are partial or full, side effects (e.g., on active conversations), or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's appropriately sized for a simple update operation and front-loaded with the core action, 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?

Given the complexity of updating a conversation flow (likely involving structured data like nodes and edges), no annotations, and no output schema, the description is incomplete. It fails to explain behavioral aspects, usage context, or what the update entails beyond the basic verb, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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 input schema already documents all parameters (conversation_flow_id, name, nodes, edges) with descriptions. The tool description adds no additional meaning beyond what the schema provides, such as explaining what 'nodes' and 'edges' represent or their structure, resulting in a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Update') and resource ('a conversation flow'), which provides a basic understanding of purpose. However, it's vague about what constitutes a 'conversation flow' and doesn't distinguish this tool from sibling tools like 'retell_update_agent' or 'retell_update_chat_agent' in terms of what specific resource it operates on.

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 no mentions of prerequisites (e.g., needing an existing conversation flow ID), exclusions, or comparisons to sibling tools like 'retell_create_conversation_flow' or 'retell_delete_conversation_flow', leaving usage context unclear.

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