Skip to main content
Glama

publishBot

publishBot

Deploy a Typebot chatbot to production using its unique bot ID via the MCP-Typebot server. Simplify publishing with a streamlined JSON interface for efficient bot management.

Instructions

Publica un Typebot existente

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botIdYes

Implementation Reference

  • The handler function that implements the publishBot tool logic. It authenticates, validates the botId, and sends a POST request to publish the Typebot.
    export async function publishBot(args: PublishBotArgs) {
      ensureAuth(); 
      const { botId } = args;
      if (!botId) throw new Error('publishBot: falta botId');
    
      const response = await axios.post(
        `https://app.typebot.io/api/v1/typebots/${botId}/publish`,
        {}
      );
      return response.data;
    }
  • TypeScript interface defining the input arguments for the publishBot handler.
    export interface PublishBotArgs {
      botId: string;
    }
  • src/index.ts:69-73 (registration)
    Configuration and registration entry for the publishBot tool in the MCP server's toolsMap, including the Zod input schema for validation.
    ['publishBot', {
      func: publishBot,
      description: 'Publica un Typebot existente',
      schema: z.object({ botId: z.string().min(1, "El campo 'botId' es obligatorio.") }),
    }],
  • src/index.ts:19-23 (registration)
    Import statement that brings the publishBot handler into the main index file for registration.
      publishBot,
      unpublishBot,
      listResults,
      startChat,
    } from './tools/bots';
Behavior2/5

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

With no annotations, the description carries full burden. 'Publica' implies a mutation (likely not read-only), but it doesn't disclose behavioral traits like permissions needed, whether publishing is reversible, rate limits, or what happens post-publish. It lacks critical context for a mutation 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 in Spanish. It's front-loaded with the core action and resource, with zero wasted words. It meets conciseness standards perfectly.

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 complexity (mutation tool), no annotations, no output schema, and 0% schema coverage, the description is incomplete. It doesn't explain what 'publish' does operationally, return values, or error conditions. It should provide more context for 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 0%, so the description must compensate. It doesn't add any parameter details beyond the schema's botId. No format, source, or constraints are explained. Baseline is 3 because the single parameter is straightforward, but the description doesn't enhance understanding.

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 'Publica un Typebot existente' clearly states the action (publish) and resource (an existing Typebot). It distinguishes from siblings like createBot (creates new) and unpublishBot (reverses this action). However, it doesn't specify what 'publish' entails operationally, keeping it from a perfect score.

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., bot must exist, be unpublished), or contrast with siblings like updateBot or startChat. Usage is implied but not explicitly stated.

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