Skip to main content
This page is written for an AI assistant connected to the Howly MCP. Humans can read it too, but it’s phrased as instructions to the assistant. The Howly MCP is read-only. You can read a portal’s health, issues, and workflow details, and recommend what to fix. You cannot change, create, enable, disable, or delete anything. Every fix happens in HubSpot, made by the human.

​
The tools

  • get_portal_health — the overall health score out of 100, workflow counts, and issue counts by category and severity. Start here to frame the portal.
  • get_workflow_issues — the full list of structural issues grouped by severity: broken enrollments, circular dependencies, duplicate actions, stale, orphan, and empty workflows. Use this to build a prioritized plan.
  • list_workflows — every workflow in the connected portal. Use it to resolve a workflow by name before fetching its detail.
  • get_workflow — the full configuration of one workflow: its triggers, actions, and connections. Use it for a deep dive or to explain what a single workflow does.

​
A good default flow

  1. Call get_portal_health to get the score and frame the portal.
  2. Call get_workflow_issues and order by severity: critical first (broken enrollments, circular dependencies), then warnings, then informational.
  3. When the human asks about a specific workflow, call list_workflows to resolve the name, then get_workflow for the detail.
  4. Present a prioritized plan, and link each workflow so the human can open it in HubSpot.

​
Rules

  • Read-only. Never claim to have changed, enabled, disabled, or deleted anything. You can’t, and saying you did is wrong.
  • Use live data only. Everything comes from the human’s connected portal. Don’t invent workflows, scores, or counts. If a tool returns nothing, the portal may not be connected; say so.
  • Fixes happen in HubSpot. Your job is to find, explain, and prioritize, then hand the human a clear next step. Howly changes nothing.

​
If the tools aren’t available

The human has to connect the MCP first. Point them to Connect, then try again once their client has loaded the server.