Skip to main content
Glama
hubspot-pipeline-mcp

hubspot-pipeline-mcp

by RynoJor

Get deal

get_deal
Read-onlyIdempotent

Retrieve a HubSpot deal's stage, owner, amount, idle days, stage history, contacts, and flagged pipeline checks with USD at risk to diagnose revenue leaks.

Instructions

One deal: stage, owner, amount, days idle, stage history, contacts, and every check it trips (stalled, duplicate contact, missing fields, weak rep), with usd_at_risk.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYesHubSpot deal id, e.g. '500002'.

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the response is not raw deal data but an evaluated record, including computed diagnostics and a derived usd_at_risk metric. It does not mention behavior for a missing/inaccessible deal id, which is the main remaining gap.

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?

A single front-loaded sentence-fragment that names the entity first, then lists the payload, ending on the most distinctive field (usd_at_risk). No filler, no repetition of what annotations or schema already state.

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 one-parameter, idempotent read with full schema coverage, complete annotations and an output schema, the description supplies everything needed to select and call it. The only omission is what happens when the deal id does not resolve, which is minor given the structured fields already provided.

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?

There is a single parameter and schema description coverage is 100%, with the schema supplying format and an example ('500002'). The description adds nothing about deal_id, so the schema does all the work; baseline 3 applies.

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?

States the resource precisely — 'One deal' — and enumerates what comes back: stage, owner, amount, days idle, stage history, contacts, tripped checks, usd_at_risk. The singular framing distinguishes it from list/aggregate siblings like pipeline_summary and find_stalled_deals without naming them. It never uses an explicit verb such as 'fetch' or 'retrieve', which keeps it just short of a 5.

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?

Usage is only implied: 'One deal' signals single-record lookup versus the multi-record siblings, and naming checks like 'stalled, duplicate contact, missing fields, weak rep' hints at where those sibling tools operate in aggregate. There is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer routing.

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