Skip to main content
Glama

delete_opportunity

DestructiveIdempotent

Remove a sales opportunity from Planhat by providing its unique ID. Use this to clean up outdated or duplicate opportunities.

Instructions

Delete a Planhat opportunity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opportunity_idYes
Behavior2/5

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

The description only repeats the action implied by the name. Annotations indicate idempotentHint=true and destructiveHint=true, but the description does not explain idempotency (e.g., what happens if the opportunity is already deleted) or any 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words, front-loading the essential information.

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

Completeness3/5

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

For a simple tool with one parameter and no output schema, the description is minimally adequate but leaves gaps in usage guidelines and behavioral transparency, making it incomplete relative to best practices.

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

Parameters2/5

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

With 0% schema description coverage, the description does not provide additional meaning for the sole parameter (opportunity_id), such as its format, source, or constraints. The parameter name is self-explanatory but no further help is given.

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 'Planhat opportunity', distinguishing it from sibling tools like delete_asset or delete_company.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool, prerequisites (e.g., existing opportunity), or consequences of deletion. It does not differentiate from other delete tools beyond the resource type.

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/da-troll/planhat-mcp'

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