Skip to main content
Glama
HubSpot MCP

HubSpot MCP

hubspot_get_capabilities

Read-onlyIdempotent

Reports HubSpot account and token access—portal details, granted scopes, daily API usage, and per-API-group status with required plan and missing scopes; refresh or probe groups as needed.

Instructions

🟢 READ-ONLY · HubSpot account access report

Reports what THIS HubSpot account and token can use: portal details, granted scopes, daily API usage, and for every API group an access status (available, missing_scopes, blocked, unverified) with the reason, the plan tier HubSpot requires and the scopes that would unlock it.

The server already ran this check at startup, probing each paid-tier or beta group with one cheap read, so a plain call returns that result without new API calls. Pass refresh=true after the token's scopes or the portal's subscription changed. probe_groups live-probes further groups, one API call each.

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

Input Schema

NameRequiredDescriptionDefault
refreshNoRun the check again instead of returning the startup result. Costs one API call per probed group. Default false.
probe_groupsNoExtra group keys to live-probe with one parameter-free read each (e.g. ["contacts"]). Implies a fresh check. Costs one API call per group.
include_api_usageNoInclude today's API usage vs. the daily limit (private-app tokens only). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly and idempotent, yet the description adds the critical behavioral fact that the check was already run at startup and cached, so a plain call costs no API calls, while refresh and probe_groups incur one call per group. That cost/rate-limit model is exactly the context annotations cannot express.

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?

Front-loaded with the read-only badge and one-line purpose, then the caching model, then parameter behavior. Slightly repetitive in restating per-group API-call costs that the schema also states, and the emoji prefix carries no semantic weight.

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?

No output schema exists, yet the description fully previews the return shape (portal details, scopes, usage, per-group status enum values, plan tier, unlock scopes), which is what an agent needs to decide to call it. For a zero-required-parameter introspection tool, nothing material is missing.

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?

Schema coverage is 100%, so baseline would be 3; the description nonetheless adds meaning by tying refresh to a lifecycle event (scope or subscription change) and noting probe_groups implies a fresh check. The private-app-only caveat for API usage is covered in the schema, so no further value is added there.

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?

States a specific verb and resource ('Reports what THIS HubSpot account and token can use') and enumerates the payload: portal details, granted scopes, API usage, per-group access status with reason, required plan tier and unlocking scopes. It is clearly a capability/introspection tool, distinguishable from siblings like hubspot_api_request or hubspot_get_endpoint.

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?

Gives concrete triggering conditions: refresh=true after token scopes or portal subscription change, and probe_groups for extra live probing. It does not name a sibling alternative nor state when NOT to call it, so it stops just short of full routing guidance, but the when-to-refresh and when-to-probe advice is explicit.

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