delete_goal
Delete a specific goal from your workspace by providing its ID.
Instructions
Delete a Goal.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal_id | Yes | Goal ID. |
Delete a specific goal from your workspace by providing its ID.
Delete a Goal.
| Name | Required | Description | Default |
|---|---|---|---|
| goal_id | Yes | Goal ID. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description must disclose behavioral traits. It only states the action without any consequences, permissions, or side effects. For a destructive operation, this is insufficient.
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 but at the cost of information. The description is under-specified rather than efficiently informative.
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?
Missing key context about the tool's effects. For a simple delete operation, details about reversibility or cascading deletion would improve completeness.
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% with one parameter 'goal_id' described as 'Goal ID.' The description adds no additional meaning beyond the schema, 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.
Does the description clearly state what the tool does and how it differs from similar tools?
Description 'Delete a Goal.' is a tautology that restates the tool name. It does not add any distinguishing context from siblings like delete_task or delete_folder.
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, prerequisites, or alternatives. The description provides no context for selecting this tool over other delete tools.
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/helbertparanhos/clickup-mcp-pro'
If you have feedback or need assistance with the MCP directory API, please join our Discord server