hubspot-mcp

hs_search_contacts

Search contacts by name, email, company, or any indexed field to quickly find relevant records. Supports full-text queries with customizable result limits.

Instructions

Full-text search across contacts by name, email, company, or any indexed field.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Full-text search string (name, email, company, etc.)
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It reveals the search behavior but omits details like read-only nature, return format, pagination, or limitations.

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?

One sentence, front-loaded with key info, no unnecessary words. Efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple parameters, description covers the search intent. But missing details on return structure and pagination for a search tool.

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 covers 'query' with a description; 'limit' lacks description (50% coverage). Description adds value by listing searchable fields, compensating for schema gaps partially.

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?

Description clearly states it performs full-text search across contacts, specifying searchable fields (name, email, company). This distinguishes it from siblings like hs_get_contact (exact) or hs_search_companies.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives like hs_crm_search or hs_contact_by_email. The description implies usage for full-text search but lacks exclusions or context.

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