Skip to main content
Glama
kanopi

@kanopi/callrail-mcp

by kanopi

Delete tracker (destructive)

delete_tracker
Destructive

Permanently delete a tracker from your CallRail account. Use this to remove trackers that are no longer needed.

Instructions

WRITE/DESTRUCTIVE: Permanently delete a tracker. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoCallRail account id. Defaults to CALLRAIL_ACCOUNT_ID if set.
tracker_idYesThe tracker id to delete.
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that deletion is permanent and cannot be undone, which is valuable behavioral context beyond annotations.

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 extremely concise with two sentences, front-loading the destructive nature. Every word adds value.

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 simple deletion tool with no output schema, the description covers the essential behavioral aspect. Could mention side effects or confirmation requirements, but overall sufficient.

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% and the description adds no additional meaning to the parameters. Baseline score of 3 is appropriate as the schema already documents them adequately.

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 it deletes a tracker permanently, with 'WRITE/DESTRUCTIVE' prefix and 'Permanently delete a tracker'. It distinguishes from sibling deletion tools like delete_company or delete_tag.

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?

While it warns that deletion cannot be undone, it does not provide guidance on when to use this tool versus alternatives or prerequisites. For a destructive tool, more context on safe usage is expected.

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/kanopi/callrail-mcp'

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