Skip to main content
Glama
pghdma

CallRail MCP

delete_tag

Permanently delete a tag definition and remove it from all associated calls and form submissions. This irreversible action cannot be undone.

Instructions

Delete a tag definition from the account. Removes it from any calls or form submissions that had it applied.

This is a HARD delete — the tag is gone permanently along with its historical applications. To preserve history, prefer renaming or disabling via update_tag instead.

Args: tag_id: Numeric tag ID. CallRail tag IDs are integers (NOT the string-prefixed format other entities use). Must match ^[0-9]+$ — accepts string or numeric forms. account_id: CallRail account ID. Auto-resolves if omitted.

Returns: JSON string {"deleted": True, "tag_id": ...} on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tag_idYes
account_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are present, so the description carries full behavioral transparency burden. It explicitly states 'HARD delete' and that the tag is gone permanently along with historical applications, disclosing the destructive nature. It also mentions the return format.

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 concise with two paragraphs plus Args/Returns. Front-loaded key action and warning. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (2 parameters, no nested objects, output schema exists), the description covers all necessary aspects: purpose, usage guidance, behavioral warnings, parameter details, and return value. It is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds detailed meaning for both parameters: explains tag_id format (numeric, integer, regex constraint) and that account_id auto-resolves if omitted. This goes beyond the schema type definitions.

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 the verb 'Delete' and the resource 'tag definition', and explains the effect of removing it from calls and form submissions. It distinguishes from siblings by explicitly mentioning 'update_tag' as an alternative for preserving history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance: it notes that deletion is permanent and advises using 'update_tag' instead to preserve history. This gives clear when-to-use and when-not-to-use context.

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

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