Skip to main content
Glama
abhinav7895

Bolna MCP Server

by abhinav7895

bolna_create_agent

Create a voice AI agent with custom system prompt, voice, LLM, and call settings for automated phone conversations.

Instructions

Create a new Bolna voice AI agent with full configuration and system prompt

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genderNoGender of the agent: "female" or "male". If not set, it is auto-detected.
languageNoTranscription language code, e.g. "en", "hi", "ta", "te"hi
voice_idNoVoice ID from bolna_list_voices, e.g. "vYENaCJHl4vFKNDYPr8y" (Riya Rao Indian Female)
llm_modelNoLLM model, e.g. "gpt-4o-mini", "gpt-4o", "claude-3-5-haiku"gpt-4o-mini
agent_nameYesUnique name for the agent
agent_typeNoAgent type, e.g. "other"other
voice_nameNoVoice name, e.g. "Riya Rao - Professional Voice"
voice_modelNoTTS model, e.g. "eleven_turbo_v2_5", "eleven_turbo_v2", "bulbul:v3"eleven_turbo_v2_5
webhook_urlNoWebhook URL to receive call events
system_promptYesLLM system prompt that governs agent behaviour
call_terminateNoMaximum call duration in seconds
voice_providerNoTTS provider for the voiceelevenlabs
incremental_delayNoDelay in ms between incremental responses
telephony_providerNoTelephony provider, e.g. "plivo" (default), "exotel"plivo
ambient_noise_trackNoAmbient noise track, e.g. "coffee-shop"
hangup_after_silenceNoSeconds of silence before hanging up
agent_welcome_messageNoFirst message the agent speaks when a call connects
number_of_words_for_interruptionNoNumber of words the caller must speak to interrupt the agent
Behavior2/5

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

No annotations are provided, and the description only mentions the action (create) without disclosing behavioral traits. It does not indicate what happens if an agent with the same name exists, whether the creation is immediate, any authentication requirements, or side effects.

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, clear sentence with no unnecessary words or repetition. It is appropriately sized and front-loaded.

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 the complexity (18 parameters, no output schema, no annotations), the description is too brief. It does not explain return values (e.g., agent ID or object), nor does it provide any context about the creation workflow or expected outcomes.

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 input schema already documents all parameters. The description adds no new semantic information beyond the schema; the baseline score of 3 applies.

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 tool's purpose: creating a new Bolna voice AI agent. It uses the verb 'create' and specifies the resource 'agent', and notes 'full configuration and system prompt', distinguishing it from sibling tools like bolna_patch_agent or bolna_list_agents.

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 on when to use this tool versus alternatives. It does not mention prerequisites, when it is appropriate to create vs update, or any disclaimers about naming conflicts.

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

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/abhinav7895/bolna-mcp'

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