delete_task_header
Permanently delete a task header by specifying its UUID. Removes the task header and related data from your CRM.
Instructions
Permanently delete a task header.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Task header UUID |
Permanently delete a task header by specifying its UUID. Removes the task header and related data from your CRM.
Permanently delete a task header.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Task header UUID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true. Description adds 'Permanently' which aligns with destructive behavior but does not disclose additional traits like cascading effects or required permissions.
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?
Extremely concise single sentence with no unnecessary words, appropriate for a simple tool.
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?
Given tool simplicity and presence of annotations/schema, the description is minimally adequate but lacks any explanation of consequences or prerequisites.
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 coverage is 100%; description adds no extra meaning beyond the schema's description of the 'id' parameter as a UUID.
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?
Description clearly states the action (delete) and the resource (task header), distinguishing it from siblings like delete_task which deletes a different entity.
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?
No guidance on when to use this tool versus alternatives (e.g., when to delete a task header vs. deleting a task). No context provided.
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/nicolascroce/keepsake-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server