delete_admin
Remove an administrator from your Campaign Monitor account by providing their email address.
Instructions
Remove an administrator from the account
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The administrator's email address |
Remove an administrator from your Campaign Monitor account by providing their email address.
Remove an administrator from the account
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The administrator's email address |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only states 'remove', implying mutation, but omits important details like destructive/irreversible nature, permission 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single clear, front-loaded sentence with no extraneous information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter delete operation, the description is minimally adequate but lacks context on what happens after deletion, error conditions, or idempotency. Given low complexity, it's borderline sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the description adds no value beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('remove'), the resource ('administrator'), and the scope ('from the account'), distinguishing it from sibling tools like add_admin and update_admin.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or consequences (e.g., cannot delete last admin).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pauliowest/cmon-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server