Skip to main content
Glama

retell_get_chat

Retrieve specific chat session details from Retell AI's agent platform to review conversations and manage interactions.

Instructions

Retrieve details of a specific chat session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYesThe unique identifier of the chat to retrieve

Implementation Reference

  • Handler logic for 'retell_get_chat' tool: extracts chat_id from args and makes a GET request to Retell API /get-chat/{chat_id} via retellRequest helper.
    case "retell_get_chat":
      return retellRequest(`/get-chat/${args.chat_id}`, "GET");
  • Input schema and metadata definition for the 'retell_get_chat' tool in the tools array.
    name: "retell_get_chat",
    description: "Retrieve details of a specific chat session.",
    inputSchema: {
      type: "object",
      properties: {
        chat_id: {
          type: "string",
          description: "The unique identifier of the chat to retrieve"
        }
      },
      required: ["chat_id"]
    }
  • src/index.ts:1283-1285 (registration)
    Registration of tool listing handler that exposes the tools array (including retell_get_chat) to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:1288-1313 (registration)
    MCP tool execution request handler that dispatches to executeTool based on tool name, handling 'retell_get_chat' via the switch case.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeTool(name, args as Record<string, unknown>);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: "text",
              text: `Error: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    });
  • Core helper function that makes authenticated HTTP requests to the Retell API, used by all tool handlers including retell_get_chat.
    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 only states it retrieves details without disclosing behavioral traits such as authentication needs, rate limits, error handling, or what 'details' include. It's vague and insufficient for a read operation tool.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero waste.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'details' are returned, potential errors, or behavioral context, leaving significant gaps for a tool that retrieves data.

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 fully documents the 'chat_id' parameter. The description adds no meaning beyond this, as it doesn't explain parameter context or usage. 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 verb 'retrieve' and resource 'details of a specific chat session', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'retell_get_call' or 'retell_get_chat_agent' that also retrieve specific resources, missing full sibling distinction.

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 like 'retell_list_chats' for listing chats or other 'retell_get_*' tools for different resources. It lacks explicit context or exclusions, offering minimal usage direction.

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