Skip to main content
Glama
HubSpot MCP

HubSpot MCP

hubspot_get_endpoint

Read-onlyIdempotent

Retrieve an endpoint's full description, safety category, plan and scope requirements, and JSON input schema by using the exact tool name returned from hubspot_search_endpoints.

Instructions

🟢 READ-ONLY · endpoint details

Return one endpoint's full description, safety category, plan/scope requirements and JSON input schema. Use the exact tool name from hubspot_search_endpoints.

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

Input Schema

NameRequiredDescriptionDefault
nameYesEndpoint tool name exactly as returned by hubspot_search_endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the leading READ-ONLY marker is largely redundant. Where the description earns credit is by disclosing the returned contents (description, safety category, plan/scope requirements, input schema), which matters because there is no output schema; it does not, however, say what happens with an unknown or misspelled name.

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?

Two short lines with zero waste: the safety marker and purpose come first, followed immediately by the prerequisite. Nothing is buried or repeated beyond necessity.

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 read tool with no output schema, the description covers what is returned and how to obtain the required name. The only minor gap is the absence of error behavior for an invalid name, which an agent would otherwise have to discover at call time.

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 coverage is 100% and the single parameter is already documented as "Endpoint tool name exactly as returned by hubspot_search_endpoints." The description restates that constraint without adding new syntax or format detail, so the schema does the heavy lifting.

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+resource ("Return one endpoint's full description") and enumerates the payload: safety category, plan/scope requirements, and JSON input schema. This clearly separates it from hubspot_search_endpoints (discovery) and hubspot_invoke_endpoint (execution).

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 an explicit prerequisite: use the exact tool name returned by hubspot_search_endpoints, which establishes the discovery-then-inspect workflow. It stops short of an explicit exclusion (e.g. "do not use to call the endpoint — use hubspot_invoke_endpoint"), so the when-not is left implicit.

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