Skip to main content
Glama

retell_get_conversation_flow

Retrieve conversation flow configurations to manage AI agent interactions within the Retell AI platform.

Instructions

Retrieve a conversation flow configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_flow_idYesThe conversation flow ID

Implementation Reference

  • The tool execution handler: switch case that calls the Retell API's get-conversation-flow endpoint using the provided conversation_flow_id argument.
    case "retell_get_conversation_flow":
      return retellRequest(`/get-conversation-flow/${args.conversation_flow_id}`, "GET");
  • Tool definition including name, description, and input schema for MCP tool listing and validation.
    {
      name: "retell_get_conversation_flow",
      description: "Retrieve a conversation flow configuration.",
      inputSchema: {
        type: "object",
        properties: {
          conversation_flow_id: {
            type: "string",
            description: "The conversation flow ID"
          }
        },
        required: ["conversation_flow_id"]
      }
    },
  • Core helper function that performs authenticated HTTP requests to the Retell AI API, implementing the actual network call for this tool.
    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();
    }
  • src/index.ts:1283-1285 (registration)
    MCP server registration for listing all tools, including this one via the 'tools' array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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. It states 'Retrieve' which implies a read operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or what happens if the ID is invalid. For a tool with zero annotation coverage, this leaves significant gaps.

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 waste. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool, 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'conversation flow configuration' entails, the return format, or error handling. For a tool with no structured data beyond the input schema, more context is needed to guide 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?

Schema description coverage is 100%, with the parameter 'conversation_flow_id' fully documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., format examples or context about where to find the ID), so it meets the baseline of 3 when 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 ('Retrieve') and resource ('conversation flow configuration'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from similar retrieval tools like 'retell_get_agent' or 'retell_get_knowledge_base' that follow the same pattern, missing sibling differentiation.

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. While the name implies it's for retrieving a specific conversation flow, there's no mention of prerequisites (e.g., needing a valid ID) or when to choose this over listing tools like 'retell_list_conversation_flows'.

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