Skip to main content
Glama
ohneben

ActiveCampaign MCP

bulk_delete_variables

DestructiveIdempotent

Delete multiple personalization variables in one call. Use with caution due to high blast radius.

Instructions

🔴 DESTRUCTIVE · bulk delete · Personalizations · DELETE /personalizations/bulkdelete

Bulk Delete Variables

Deletes many records in a single call. High blast radius — always confirm before calling.

Bulk delete personalization variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoList of variables to be deleted, ie: 1,2,3
Behavior4/5

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

Annotations already indicate destructiveHint=true, but the description adds useful behavioral context by emphasizing the high blast radius and the need for confirmation. No contradictions with annotations.

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?

The description is relatively concise but includes some repetition (e.g., 'Bulk Delete Variables' and 'Bulk delete personalization variables'). It is front-loaded with critical information (destructive hint, endpoint). Each sentence adds value, though minor redundancy exists.

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

Completeness4/5

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

For a delete tool with no output schema, the description sufficiently covers purpose, caution, and resource type. It lacks mention of idempotency (though annotation says idempotentHint=true), but overall it is complete enough for the agent to use correctly.

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% for the single 'ids' parameter, which the schema describes as 'List of variables to be deleted, ie: 1,2,3'. The description does not add further semantics beyond what the schema provides, so baseline score of 3 is appropriate.

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 'Bulk Delete Variables' and 'Deletes many records in a single call', providing a specific verb and resource. It distinguishes from sibling tools like 'delete_variable' (single delete) and other bulk operations.

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 includes a cautionary note 'High blast radius — always confirm before calling', which gives usage guidance. However, it does not explicitly compare to alternatives (e.g., when to use delete_variable instead), so the guidance is implicit.

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/ohneben/ActiveCampaign-MCP'

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