hubspot-mcp

hs_get_email_campaign_stats

Retrieve opens, clicks, bounces, and unsubscribes for a HubSpot marketing email using its ID.

Instructions

Get performance statistics (opens, clicks, bounces, unsubscribes) for a specific marketing email.

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": {
      "emailId": "<emailId>"
    },
    "name": "hs_get_email_campaign_stats"
  }
}

Input Schema

Name	Required	Description	Default
`emailId`	Yes	HubSpot marketing email ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 26, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not mention read-only behavior, authentication needs, rate limits, or return format. For a tool that retrieves data, more behavioral context is expected beyond listing metric names.

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?

One concise sentence that efficiently conveys the tool's purpose and the metrics involved. No wasted words or redundancy.

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 simple tool with one parameter and no output schema, the description adequately covers what it does and what metrics are returned. It lacks details on return format but is sufficient for a single-purpose tool.

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% (the single parameter emailId is described as 'HubSpot marketing email ID'). The description reiterates 'specific marketing email' but adds no new semantic meaning beyond the schema. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Get' and the resource 'performance statistics for a specific marketing email', listing the specific metrics (opens, clicks, bounces, unsubscribes). It distinguishes from siblings like hs_list_marketing_emails which lists emails rather than providing stats.

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

Usage Guidelines4/5

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

The description implies use when stats for a specific email are needed. No explicit when-not or alternative is given, but the context is clear enough given the single purpose.

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