hubspot-mcp

hs_pipeline_summary

Aggregate deal counts and total amounts by pipeline stage to get a quick funnel snapshot for a specified pipeline.

Instructions

Deal counts and total amounts aggregated by pipeline stage — a quick funnel snapshot for a given pipeline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipelineId": "<pipelineId>"
    },
    "name": "hs_pipeline_summary"
  }
}

Input Schema

Name	Required	Description	Default
`pipelineId`	Yes	Pipeline ID (from list_pipelines)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 26, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Lacks detail on e.g., whether all stages are returned, read-only nature, or any limits. 'Aggregated by pipeline stage' is present but not expanded.

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?

Single sentence, front-loaded, no redundant words. Efficient and to the point.

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

Completeness3/5

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

Adequate for a simple 1-param tool with no output schema, but could benefit from describing the output shape (e.g., per-stage breakdown, totals).

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% with pipelineId having a clear description. The tool description adds 'for a given pipeline' which is consistent but not new information.

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 'deal counts and total amounts aggregated by pipeline stage', a specific verb+resource combination. Distinguishes from siblings like hs_deals_by_stage by focusing on aggregated metrics.

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?

No explicit guidance on when to use vs alternatives. Implies a 'quick funnel snapshot' but doesn't contrast with hs_deals_by_stage or other similar tools.

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