Skip to main content
Glama
abhinav7895

Bolna MCP Server

by abhinav7895

bolna_delete_batch

Delete a batch campaign permanently by providing its unique batch ID. Clean up completed or unwanted campaigns from your Bolna account.

Instructions

Permanently delete a batch campaign by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
batch_idYesThe batch ID to delete
Behavior2/5

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

Annotations are absent, so description carries full burden. It mentions 'Permanently delete' implying destructiveness, but lacks details on side effects (e.g., cascade deletions), authorization needs, or irreversibility. For a destructive operation, this is insufficient.

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

Conciseness3/5

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

The description is a single efficient sentence with no waste, but given the destructive nature, it is too brief and could benefit from additional context while remaining concise.

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?

Despite low complexity (1 required param, no output schema), the description lacks completeness by not explaining consequences, return value, or error handling. It is minimal but leaves gaps for an agent to understand full impact.

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?

Only one parameter (batch_id) with schema description 'The batch ID to delete'. Schema coverage is 100%, and the description adds no extra meaning beyond the schema. 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 'Permanently delete a batch campaign by its ID', which specifies the verb (delete) and resource (batch campaign), distinguishing it from sibling tools like bolna_create_batch or bolna_stop_batch.

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 (e.g., stopping vs. deleting), no prerequisites or exclusions provided. The description only states the action without contextual usage advice.

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