Skip to main content
Glama
HubSpot MCP

HubSpot MCP

hubspot_search_endpoints

Read-onlyIdempotent

Search a HubSpot endpoint tool catalog by keyword, group, area, or safety category to find usable API actions and view method, path, API, and token access status.

Instructions

๐ŸŸข READ-ONLY ยท endpoint catalog search

Search this server's catalog of 687 HubSpot endpoint tools by keyword, group, area or safety category. Returns one compact line per tool (name, method+path, category, API; consolidated tools also list the values of their selector argument, e.g. objectType). Each line also says whether this token can use the tool, from the access check the server ran at startup.

Workflow: search here โ†’ hubspot_get_endpoint for the input schema โ†’ hubspot_invoke_endpoint to call it.

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_search_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoHubSpot area filter (e.g. "CRM", "CMS", "Marketing").
groupNoExact group key filter (e.g. "contacts", "marketing-emails").
limitNoPage size (default 40).
queryNoKeywords matched against name, path, API name and summary (e.g. "create deal", "hubdb rows").
offsetNoPagination offset (default 0).
categoryNoSafety-category filter.
usable_onlyNoOnly return tools this token can use according to the startup access check. Default false.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint, openWorldHint), so the description's added value is elsewhere: it discloses the return shape ('one compact line per tool' with name, method+path, category, API, selector values) and that per-token usability comes from a startup access check. The '๐ŸŸข READ-ONLY' badge merely restates the annotation, but the rest is genuine behavioral context that exists nowhere else given there is no output schema.

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?

Three short blocks โ€” safety badge, purpose/filter sentence, return-format sentence, workflow line โ€” with the identifying information front-loaded and no filler. Every sentence contributes either routing or result-shape information.

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?

For a seven-parameter, all-optional discovery tool with no output schema, the description supplies the two things the schema cannot: what a result line contains and how this call chains into get/invoke. Nothing an agent needs in order to search correctly is missing.

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 all seven parameters including the category enum and the usable_only startup-check semantics are already documented structurally. The description's 'keyword, group, area or safety category' phrasing restates the same filter axes without adding format or interaction rules, so the 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 ('Search this server's catalog of 687 HubSpot endpoint tools') plus the filter axes, and frames the tool's role in a three-step chain. An agent can distinguish it from hubspot_get_endpoint and hubspot_invoke_endpoint purely from this text.

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 'Workflow: search here โ†’ hubspot_get_endpoint for the input schema โ†’ hubspot_invoke_endpoint to call it' line gives explicit routing to the correct sibling at each stage. It stops short of stating when NOT to use this tool (e.g. when the endpoint name is already known and a direct invoke would suffice), which keeps it off a 5.

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