Skip to main content
Glama

updateBot

updateBot

Modify an existing Typebot by updating its properties such as name through the MCP-Typebot server, using a structured JSON input with botId and typebot details.

Instructions

Actualiza un Typebot existente (p.ej. cambia nombre)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botIdYes
overwriteNo
typebotYes

Implementation Reference

  • The core handler function implementing the updateBot tool. It authenticates, fetches the current bot version, applies changes via PATCH to the Typebot API, and returns the result.
    export async function updateBot(args: UpdateBotArgs) {
      ensureAuth();
    
      const { botId, typebot: changes, overwrite = false } = args;
      if (!botId) throw new Error('updateBot: falta botId');
      if (typeof changes !== 'object' || Object.keys(changes).length === 0) {
        throw new Error(
          'updateBot: el objeto `typebot` con campos a cambiar es obligatorio'
        );
      }
    
      const getRes = await axios.get<{ typebot: { version: string } }>(
        `https://app.typebot.io/api/v1/typebots/${botId}`
      );
      const version = getRes.data.typebot.version;
      if (!version) {
        throw new Error(
          'updateBot: no pude obtener la versión actual del Typebot'
        );
      }
    
      const payload: Record<string, any> = {
        typebot: {
          version,
          ...changes
        }
      };
      if (overwrite) {
        payload.overwrite = true;
      }
    
      const patchRes = await axios.patch(
        `https://app.typebot.io/api/v1/typebots/${botId}`,
        payload
      );
      return patchRes.data;
    }
  • TypeScript interface defining the input schema for the updateBot function.
    export interface UpdateBotArgs {
      botId: string;
      typebot: Record<string, any>; 
      overwrite?: boolean;
    }
  • src/index.ts:55-63 (registration)
    Registration entry for the updateBot tool in the toolsMap, including the handler function reference, description, and Zod input schema for MCP server registration.
    ['updateBot', {
      func: updateBot,
      description: 'Actualiza un Typebot existente (p.ej. cambia nombre)',
      schema: z.object({
        botId:     z.string().min(1, "El campo 'botId' es obligatorio."),
        typebot:   z.record(z.any()).refine(x => typeof x === 'object', "El campo 'typebot' es obligatorio."),
        overwrite: z.boolean().optional(),
      }),
    }],
  • Zod schema used for input validation of updateBot tool in the MCP server.
    schema: z.object({
      botId:     z.string().min(1, "El campo 'botId' es obligatorio."),
      typebot:   z.record(z.any()).refine(x => typeof x === 'object', "El campo 'typebot' es obligatorio."),
      overwrite: z.boolean().optional(),
    }),
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 this is an update operation but doesn't describe what happens when overwrite=true/false, whether changes are reversible, what permissions are required, or what the response looks like. For a mutation tool with 3 parameters and no annotation coverage, this is insufficient.

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 extremely concise - a single sentence in Spanish that directly states the purpose with a helpful example. Every word earns its place with no wasted text, though it could benefit from being more comprehensive.

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?

For a mutation tool with 3 parameters, nested objects, no annotations, and no output schema, the description is incomplete. It doesn't explain the update behavior, parameter meanings, return values, or how this tool fits within the broader Typebot management workflow with its 7 sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for all 3 parameters, the description provides minimal help. It mentions changing the name as an example, which hints at the 'typebot' parameter's purpose, but doesn't explain botId (required identifier) or overwrite (boolean flag). The description doesn't compensate for the complete lack of schema 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 ('Actualiza' - updates) and resource ('un Typebot existente'), providing a specific example of changing the name. It distinguishes from createBot by specifying 'existente' (existing), but doesn't explicitly differentiate from other sibling tools like publishBot or unpublishBot.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (like needing an existing bot), when not to use it, or how it relates to sibling tools like publishBot/unpublishBot for workflow sequencing.

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

Related 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/osdeibi/MCP-typebot'

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