Skip to main content
Glama
nubiia-dev

@iamsamuelfraga/mcp-hubspot

by nubiia-dev

hubspot_workflows_delete

Permanently delete a HubSpot automation workflow. This action is irreversible; disable the workflow instead if you may need it later. Requires the automation OAuth scope.

Instructions

[BETA] WARNING: IRREVERSIBLE. Delete an automation workflow (flow) from HubSpot. The workflow CANNOT be recovered after deletion via the API. Consider disabling the flow (isEnabled: false) instead if you may need it later. Use hubspot_workflows_get to confirm the flow ID before proceeding. Requires the "automation" OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowIdYesThe v4 flow ID of the workflow to permanently delete. WARNING: This action is IRREVERSIBLE and cannot be undone via the API.
Behavior4/5

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

No annotations provided, so description carries full burden. Clearly warns that deletion is irreversible and cannot be undone via the API. Mentions OAuth scope requirement. Could add response format or side effects but is sufficient for a delete tool.

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?

Concise, front-loaded with BETA and WARNING. Every sentence adds necessary context 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?

Completely covers what the tool does, its irreversible nature, alternative action, prerequisite step, and authentication requirement. No output schema, but for a delete tool this is adequate.

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

Parameters4/5

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

Schema coverage is 100%, so baseline 3. Description adds value by repeating the irreversibility warning and suggesting to confirm the flow ID first, which goes beyond schema description.

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?

Clearly states it deletes an automation workflow irreversibly. Specifies the resource and action, and is distinct from sibling workflow tools like get, list, create, etc.

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?

Explicitly advises to consider disabling instead of deleting if the workflow might be needed later. Recommends using hubspot_workflows_get to confirm the flow ID before proceeding.

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/nubiia-dev/mcp-hubspot'

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