Skip to main content
Glama
HubSpot MCP

HubSpot MCP

hubspot_api_request

Destructive

Send arbitrary HTTP requests to HubSpot API paths for new or beta endpoints. Server-side auth, rate limiting, timeouts, and retries handle the request.

Instructions

๐Ÿ”ด ADVANCED ยท raw HubSpot API request

Perform an arbitrary HTTP request against the HubSpot API host โ€” the escape hatch for brand-new or beta endpoints that don't have a dedicated tool (yet). Auth, rate limiting, timeouts and retries are still handled server-side.

Host is fixed to https://api.hubapi.com; pass only the path (e.g. "/crm/v3/objects/contacts"). PREFER the dedicated tools: they carry accurate schemas and safety categories. This tool can execute ANY method, including destructive ones โ€” state the method and path clearly and get user confirmation for writes/deletes.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "hubspot_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional request body. Objects are sent as JSON (or as form fields for form content types).
pathYesAPI path starting with "/", e.g. "/crm/v3/objects/contacts". The host is fixed server-side.
queryNoOptional query parameters. Array values are repeated (properties=a&properties=b).
methodYesHTTP method.
contentTypeNoRequest body content type (default application/json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds substantive context the agent could not infer: auth, rate limiting, timeouts and retries are handled server-side, and the host is fixed to https://api.hubapi.com. It also spells out the confirmation requirement for writes/deletes, which is real behavioral guidance. It stops short of describing response format or error behavior, so it is not a full 5.

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?

Content is front-loaded: what it is, then the host constraint, then the prefer-dedicated-tools warning, then the confirmation caveat. The emoji header and bold styling are slightly noisy, but every sentence carries an actionable fact and nothing is redundant.

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 5-parameter, fully schema-documented, annotation-covered escape-hatch tool with no output schema, the description covers host scoping, server-side concerns, safety routing and confirmation. The main remaining gap is what a response or error looks like, which is a reasonable omission given the tool's arbitrary nature.

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%, so every parameter is already documented in the schema; the description only reinforces the path format ('pass only the path') and the fact that the host is fixed server-side. That is useful disambiguation but largely duplicates structured data, so baseline 3 applies.

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: 'Perform an arbitrary HTTP request against the HubSpot API host', and frames it as 'the escape hatch for brand-new or beta endpoints that don't have a dedicated tool'. This immediately distinguishes it from the dedicated-tool siblings without requiring the agent to open any schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it (brand-new or beta endpoints lacking a dedicated tool) and when not to ('PREFER the dedicated tools: they carry accurate schemas and safety categories'). It also gives an operational precondition: 'state the method and path clearly and get user confirmation for writes/deletes.'

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