Skip to main content
Glama

deleteBot

deleteBot

Remove a Typebot chatbot by specifying its unique bot ID using this tool on the MCP-Typebot server.

Instructions

Elimina un Typebot por su ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botIdYes

Implementation Reference

  • The main handler function for the 'deleteBot' tool. It ensures authentication, validates the botId, and sends a DELETE request to the Typebot API to delete the specified bot.
    export async function deleteBot(args: DeleteBotArgs) {
      ensureAuth(); 
      const { botId } = args;
      if (!botId) throw new Error('deleteBot: falta botId');
    
      const response = await axios.delete(
        `https://app.typebot.io/api/v1/typebots/${botId}`
      );
      return response.data;
    }
  • TypeScript interface defining the input arguments for the deleteBot function, requiring a botId string.
    export interface DeleteBotArgs {
      botId: string;
    }
  • src/index.ts:64-68 (registration)
    Registration of the 'deleteBot' tool in the MCP server's toolsMap. Specifies the handler function, description, and Zod input schema for validation.
    ['deleteBot', {
      func: deleteBot,
      description: 'Elimina un Typebot por su ID',
      schema: z.object({ botId: z.string().min(1, "El campo 'botId' es obligatorio.") }),
    }],
  • Zod schema used for input validation of the 'deleteBot' tool during registration, ensuring botId is a non-empty string.
    schema: z.object({ botId: z.string().min(1, "El campo 'botId' es obligatorio.") }),
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a deletion operation, implying it's destructive, but doesn't disclose whether deletion is permanent/irreversible, what permissions are required, whether it affects associated data, or what happens on success/failure. For a destructive tool with zero annotation coverage, this is a significant gap.

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 Spanish sentence that directly states the tool's function. There's zero wasted verbiage and it's front-loaded with the core action.

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 destructive deletion tool with no annotations, no output schema, and minimal parameter documentation, the description is inadequate. It doesn't address critical behavioral aspects like permanence, side effects, error conditions, or return values that an agent would need to use this tool safely and effectively.

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 description adds minimal meaning beyond the input schema. It specifies that the parameter is a bot ID, which the schema already indicates through the property name 'botId'. With 0% schema description coverage and only 1 parameter, the baseline would be 4, but the description doesn't compensate with format details, validation rules, or examples.

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 ('Elimina' - deletes) and the resource ('un Typebot por su ID'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'unpublishBot', which might also involve removing or disabling a bot in some way.

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. With siblings like 'unpublishBot' and 'deleteBot' existing, the description doesn't clarify whether deletion is permanent versus unpublishing, or what prerequisites might be needed before deletion.

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