Skip to main content
Glama
abhinav7895

Bolna MCP Server

by abhinav7895

bolna_update_agent

Update an existing voice AI agent's configuration and system prompt to modify its behavior, welcome message, or call settings.

Instructions

Update an existing Bolna agent's configuration and/or system prompt

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genderNoGender of the agent: "female" or "male". If not set, it is auto-detected.
agent_idYesThe unique ID of the agent to update
agent_nameNoNew name for the agent
agent_typeNoAgent type
webhook_urlNoNew webhook URL
system_promptNoNew LLM system prompt
call_terminateNoMax call duration in seconds
incremental_delayNoDelay in ms between incremental responses
telephony_providerNoTelephony provider, e.g. "plivo" (default), "exotel"
ambient_noise_trackNoAmbient noise track
hangup_after_silenceNoSeconds of silence before hanging up
agent_welcome_messageNoNew welcome message
number_of_words_for_interruptionNoWords to interrupt
Behavior2/5

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

No annotations provided; the description only states 'update' without disclosing whether it merges or replaces, permissions required, or side effects. Insufficient for a mutation tool with 13 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One concise sentence, but lacks structured formatting. Efficient yet minimal.

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?

With 13 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values or confirm success, leaving gaps for agent invocation.

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 coverage is 100% with all parameters documented. The description adds no extra value beyond the schema, so baseline 3 is appropriate.

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 (Update) and the resource (existing Bolna agent's configuration and/or system prompt). It distinguishes from create/delete agents but leaves ambiguity with bolna_patch_agent.

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 on when to use this tool versus alternatives like bolna_patch_agent or bolna_create_agent. Missing prerequisites or context for updating.

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