Skip to main content
Glama
mantis-productions

hubspot-mcp-server

Search HubSpot CRM

hubspot_search
Read-onlyIdempotent

Search HubSpot CRM objects (contacts, companies, deals) using full-text queries and property filters to find specific records.

Instructions

Search contacts, companies, or deals using full-text query and/or property filters.

Args:

  • objectType: "contacts" | "companies" | "deals"

  • query (string): Full-text search string (e.g. "Acme Corp" or "john@example.com")

  • filters: Array of property filters: [{ propertyName: "email", operator: "EQ", value: "john@example.com" }] Operators: EQ, NEQ, CONTAINS_TOKEN, NOT_CONTAINS_TOKEN, GT, GTE, LT, LTE, HAS_PROPERTY, NOT_HAS_PROPERTY

  • properties (string[]): Property names to include in results

  • sortBy (string): Property name to sort by

  • sortDirection: "ASCENDING" | "DESCENDING"

  • limit (number): 1-100 results (default 20)

  • after (string): Pagination cursor

Returns: { total: number, results: HubSpotRecord[], hasMore: boolean, nextCursor?: string }

Examples:

  • Find a contact by email: objectType="contacts", filters=[{propertyName:"email",operator:"EQ",value:"jane@example.com"}]

  • Find open deals: objectType="deals", filters=[{propertyName:"dealstage",operator:"NEQ",value:"closedwon"}]

  • Find companies in a city: objectType="companies", filters=[{propertyName:"city",operator:"EQ",value:"Boston"}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectTypeYesCRM object type to search
queryNoFull-text search query string
filtersNoProperty filters to narrow results
propertiesNoProperty names to include in the response
sortByNoProperty name to sort by
sortDirectionNoSort directionASCENDING
limitNoNumber of results (1-100)
afterNoPagination cursor
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context: pagination details (hasMore, after), default limit, and that search returns structured results. No contradictions.

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?

The description is well-structured with clear sections (Args, Returns, Examples), front-loaded with purpose. While verbose, every sentence adds value, making it suitable for agent use.

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?

Given 8 parameters, 100% schema coverage, detailed examples, and return structure explanation (even without output schema), the description covers all necessary context for correct invocation, including pagination and filter operator details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description significantly enriches understanding: it explains the filter array structure with 10 operators, provides examples, and details the return object. This goes well beyond schema descriptions.

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 'Search contacts, companies, or deals using full-text query and/or property filters.' This identifies a specific verb (search) and resource (CRM objects), distinguishing it from sibling tools like hubspot_list_* which list all records, and hubspot_get_* which fetch by ID.

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 provides examples (find contact by email, open deals, companies in city) that imply appropriate contexts. However, it does not explicitly state when to use this instead of list tools or other search alternatives, and lacks exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mantis-productions/hubspot-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server