Skip to main content
Glama

retell_get_agent_versions

Retrieve version history for an AI agent to track changes, compare iterations, and manage updates within the Retell AI platform.

Instructions

Retrieve the version history of an agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYesThe agent ID to get versions for

Implementation Reference

  • src/index.ts:592-605 (registration)
    Tool registration entry in the tools array, including name, description, and input schema definition.
    {
      name: "retell_get_agent_versions",
      description: "Retrieve the version history of an agent.",
      inputSchema: {
        type: "object",
        properties: {
          agent_id: {
            type: "string",
            description: "The agent ID to get versions for"
          }
        },
        required: ["agent_id"]
      }
    },
  • Input schema for validating the tool's arguments, requiring an agent_id string.
    inputSchema: {
      type: "object",
      properties: {
        agent_id: {
          type: "string",
          description: "The agent ID to get versions for"
        }
      },
      required: ["agent_id"]
    }
  • Handler implementation within the executeTool switch statement, which performs a GET request to the Retell API endpoint `/get-agent-versions/{agent_id}` using the shared retellRequest helper.
    case "retell_get_agent_versions":
      return retellRequest(`/get-agent-versions/${args.agent_id}`, "GET");
  • src/index.ts:1283-1285 (registration)
    MCP server registration for listing all tools, which exposes the retell_get_agent_versions tool via the tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:1287-1293 (registration)
    MCP server registration for tool execution requests, which routes to executeTool based on the tool name.
    // 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves data, implying it's a read-only operation, but doesn't clarify aspects like authentication requirements, rate limits, pagination for multiple versions, error conditions, or what 'version history' entails (e.g., timestamps, changes). For a retrieval tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 is front-loaded with the core action and resource, making it easy to parse quickly. There is no wasted language or redundancy.

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?

For a simple retrieval tool with one parameter and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects (e.g., response format, error handling) and usage context. Without annotations or output schema, the description should provide more completeness, but it meets a bare minimum for understanding what the tool does.

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 input schema has 100% description coverage, with the single parameter 'agent_id' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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 ('version history of an agent'), making the purpose immediately understandable. It distinguishes this tool from other retrieval tools like 'retell_get_agent' by specifying it fetches version history rather than current agent details. However, it doesn't explicitly differentiate from all sibling tools beyond this implicit scope.

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. It doesn't mention prerequisites (e.g., needing an existing agent), compare it to similar tools like 'retell_get_agent' or 'retell_list_agents', or specify use cases for accessing version history versus current state. Usage is implied but not articulated.

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