Botsify

Create agent

create-agent

Create a Botsify agent via POST /v1/create-bot. Requires agent_type chatbot, agent, or voice. Optional marketplace template slug. Stores the new bot_api_key for later tools.

Input Schema

TableJSON Schema

Name	Required	Description
`bot_name`	Yes	Display name for the new agent
`template`	No	Marketplace template slug when cloning a template agent
`agent_type`	Yes	Agent kind: chatbot for widgets, agent for autonomous AI, voice for phone agents

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	JSON or plain text body returned by the Botsify HTTP API

TDQS

A4.1/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false, so mutation is expected. The description adds valuable context by disclosing the side effect: 'Stores the new bot_api_key for later tools.' This is beyond what annotations provide, though it does not cover additional behavioral aspects like authentication or idempotency.

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 two sentences, front-loaded with the primary action and endpoint. Every clause adds value: creation action, required type, optional template, and side effect. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple create operation, the description covers the essential aspects: what it does, required types, optional template, and the important side effect of storing the bot_api_key. The presence of an output schema and comprehensive parameter schema means the description does not need to explain return values or parameter details. It is sufficiently complete for an agent to select and invoke this tool.

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 100%, so the baseline is 3. The description repeats information already in the schema (agent_type values, template optionality) but does not add new meaning beyond the schema. It does not explain how bot_name is used or any format constraints beyond what's in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a Botsify agent'), the resource ('agent'), and the specific API endpoint ('POST /v1/create-bot'). This is more specific than the tool name alone and distinguishes it from sibling tools like clone-agent or rename-agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (creating an agent) but does not explicitly mention alternatives or when-not-to-use scenarios. For example, it does not differentiate from clone-agent, which is a related sibling. The statement 'Requires agent_type chatbot, agent, or voice' gives parameter constraints, not when-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Botsify tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Several tools have overlapping purposes, such as send-converse-message, send-inbox-message, send-user-message, and stream-user-message, which all deliver messages but with subtle differences. Similarly, list-bot-messenger-users and list-messenger-users both fetch messenger users, and start-builder-chat, clear-builder-conversation, and store-builder-response all manage builder chat state. Descriptions help, but the boundaries are still confusing.

Naming Consistency3/5

Tool names consistently use hyphenated lowercase verb-noun format, but the verbs and nouns vary significantly in specificity. For example, 'get-query-response' vs 'query-mcp-agent' vs 'stream-user-message' all imply querying but with different styles. The pattern is readable but not highly predictable, with some names like 'change-user-activation' and 'patch-instruction-section' deviating from the simple verb_object structure.

Tool Count2/5

With 44 tools, this server feels overloaded. The breadth covers bots, messaging, templates, whitelabel, and versions, but many tools could be consolidated (e.g., multiple message-sending variants). The count exceeds the 25-tool threshold for 'too many', making it difficult for agents to select the right tool without extensive context.

Completeness4/5

The tool set covers the main lifecycle: agent creation, versioning, deployment, deletion, messaging, conversation history, user management, template management, and whitelabel operations. Minor gaps exist, such as missing delete for WhatsApp templates or update operations for user attributes, but these are workable edge cases. Core workflows are well supported.

Resources

Need Help?