Skip to main content
Glama

listBots

listBots

Retrieve a list of all Typebots in a specific workspace using the workspace ID. Manage and organize your chatbot projects effectively with this streamlined JSON-based tool.

Instructions

Lista todos los Typebots de un workspace

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNo

Implementation Reference

  • The core handler function that executes the listBots tool: authenticates the request, resolves the workspaceId from args or environment, queries the Typebot API for typebots in that workspace, and returns the response data.
    export async function listBots(args: ListBotsArgs = {}) {
      ensureAuth(); 
      const workspaceId =
        args.workspaceId || process.env.TYPEBOT_WORKSPACE_ID;
      if (!workspaceId) {
        throw new Error(
          'listBots: falta workspaceId (ni en args ni en process.env)'
        );
      }
    
      const response = await axios.get(
        'https://app.typebot.io/api/v1/typebots',
        { params: { workspaceId } }
      );
      return response.data;
    }
  • TypeScript interface defining the expected input arguments for the listBots handler function.
    export interface ListBotsArgs {
      workspaceId?: string;
    }
  • src/index.ts:45-49 (registration)
    Tool registration entry in the toolsMap: associates the name 'listBots' with its handler function, description, and Zod input schema. This map is used in a loop to register each tool with the MCP server via server.registerTool.
    ['listBots', {
      func: listBots,
      description: 'Lista todos los Typebots de un workspace',
      schema: z.object({ workspaceId: z.string().optional() }),
    }],
  • Zod schema used for input validation of the listBots tool during MCP registration.
    schema: z.object({ workspaceId: z.string().optional() }),
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it lists all Typebots, implying a read-only operation, but doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what happens if workspaceId is omitted (since it's not required). This leaves significant gaps for a tool with no annotation coverage.

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 that directly states the tool's action without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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, 0% schema coverage, no output schema, and multiple sibling tools, the description is incomplete. It lacks details on behavior, parameters, and usage context, making it inadequate for a tool in this complex environment. A simple list operation needs more guidance to be fully actionable.

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?

Schema description coverage is 0%, and the description doesn't add any parameter semantics. It mentions 'de un workspace' which relates to the workspaceId parameter, but doesn't explain its format, source, or implications. With one undocumented parameter and no compensation in the description, this falls short of the baseline.

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 ('Lista todos los') and resource ('Typebots de un workspace'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getBot' (which might retrieve a single bot) or 'listResults' (which lists results rather than bots), missing full sibling differentiation.

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 a workspaceId), exclusions, or comparisons to siblings like 'getBot' for single bots or 'listResults' for different data. Usage is implied by the action but not explicitly defined.

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