Skip to main content
Glama
hubspot-pipeline-mcp

hubspot-pipeline-mcp

by RynoJor

Pipeline summary

pipeline_summary
Read-onlyIdempotent

Summarizes HubSpot pipeline health by stage: deal counts and values, conversion and win rates, plus stalled deals idle 30+ days as USD-at-risk and open/won totals.

Instructions

By stage: deal count, value, how many reached it, the rate to the next stage, the win rate from that stage, and stalled deals (idle 30+ days) as usd_at_risk. Plus pipeline totals: open value, won value, win rate.

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": "pipeline_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuinely behavioral detail beyond that: the 'stalled' definition of idle 30+ days and its exposure as usd_at_risk. Beyond that it mostly restates return values that the output schema already carries, and it never says what time window the metrics cover.

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

Conciseness3/5

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

It is short with no filler, but it is a single comma-chained fragment that leads with field names instead of stating what the tool returns as a whole. Given that an output schema exists, much of the enumeration is redundant and could be collapsed into a purpose statement plus the one non-obvious metric definition.

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

Completeness4/5

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

For a zero-parameter, read-only tool with full annotations and an output schema, the definition supplies enough to call it correctly: metrics described and the 30-day stall threshold defined. The remaining gap is scope — no statement of the time period or pipeline coverage the totals reflect — which matters for interpreting 'open value' and 'won value'.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The one caveat is that with zero parameters the reporting period is undefined, which is a scope question rather than a parameter one.

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 description makes clear this is a per-stage pipeline metrics report, naming the concrete measures (deal count, value, stage conversion rate, win rate, stalled value). However, it is written as an enumeration of output fields rather than a verb+resource statement, and it never distinguishes itself from siblings like rep_conversion or find_stalled_deals, even though it overlaps with both.

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?

There is no when-to-use guidance, no stated alternatives, and no exclusions. An agent must infer from the metric list alone whether this or rep_conversion is the right call for a conversion question, and nothing tells it when find_stalled_deals would be the better choice.

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