Skip to main content
Glama
hubspot-pipeline-mcp

hubspot-pipeline-mcp

by RynoJor

Find stalled deals

find_stalled_deals
Read-onlyIdempotent

Identify open deals stalled in a stage with no activity for a set number of days, then return counts, USD at risk, and the largest deals to prioritize follow-up.

Instructions

Open deals sitting in a stage with no activity for days_idle+ days.

Returns count, usd_at_risk (sum of their amounts) and the largest deals first: id, name, owner, amount_usd, last_activity, days_idle.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_stalled_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to list (totals always cover every match).
stageNoDeal stage label or id, e.g. 'Proposal'. Case-insensitive.Proposal
days_idleNoMinimum days since last activity.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful behavioral detail beyond that: it limits results to open deals, applies an idle threshold, and explains the aggregate and sorted return shape.

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?

Two compact sentences front-load the filter criteria and then summarize the returned data. The explicit field list is slightly redundant with the output schema, but the description remains efficient overall.

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 read-only query with rich annotations, 100% parameter schema coverage, and an output schema, the description supplies enough context to select and call the tool correctly. Missing sibling routing is a usage-guidance gap rather than a completeness gap.

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?

Schema description coverage is 100%, so limit, stage, and days_idle are already documented in the schema. The description reinforces the days_idle threshold and stage filtering and hints at largest-first ordering, but adds no new syntax or edge-case semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource with precise filter criteria: open deals, a given stage, and no activity for days_idle+ days. It does not explicitly contrast with siblings such as pipeline_summary or get_deal, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The description defines the query condition clearly enough to imply when it applies, but it gives no explicit when-to-use or when-not guidance. It also does not name alternatives such as get_deal or pipeline_summary, so usage remains implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.