Skip to main content
Glama
mantis-productions

hubspot-mcp-server

Delete HubSpot Deal

hubspot_delete_deal
DestructiveIdempotent

Archive a deal in HubSpot CRM by moving it to the recycle bin, allowing future restoration.

Instructions

Archive (soft-delete) a deal in HubSpot. Record moves to the recycle bin and can be restored.

Args:

  • dealId (string): HubSpot deal record ID

Returns: Confirmation message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dealIdYesHubSpot deal record ID to archive
Behavior5/5

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

The description adds critical behavioral context beyond annotations: it specifies that deletion is a soft-delete (move to recycle bin) and restorable, which supplements the destructiveHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is short and to the point, but includes a redundant 'Args:' section that echoes the single parameter already documented in the schema. Minor inefficiency.

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?

For a simple tool with one parameter, annotations, and no output schema, the description adequately covers the action, consequences (soft-delete, restorable), and return (confirmation message).

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?

The parameter is fully described in the input schema (100% coverage). The description repeats the parameter but adds no new semantic information beyond what the schema provides.

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 action ('Archive') and the resource ('deal'), and distinguishes it from other HubSpot tools by specifying it's a soft-delete that can be restored.

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

Usage Guidelines4/5

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

The description explains the soft-delete nature and recovery option, suggesting when to use it, but does not explicitly state when not to use or mention alternatives.

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/mantis-productions/hubspot-mcp-server'

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