Skip to main content
Glama
Sign In
mcpship-hubspot

mcpship-hubspot

by onemore-coder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_contacts

Search HubSpot contacts by name, email, or company, or list recently modified contacts when no query is provided.

Instructions

Search HubSpot contacts by name, email, or company. With no query, returns the most recently modified contacts.

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": "search_contacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (HubSpot caps a page at 100).
queryNoFree-text search, e.g. a person's name, email, or company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. The no-query default (most recently modified contacts) is genuinely useful behavior not derivable from the schema, but pagination, ordering for query results, and permission requirements go unmentioned.

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 sentences, front-loaded with the core action, and the default behavior placed second. Nothing is wasted or repeated.

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 two-optional-parameter read tool with no output schema, the description plus schema covers what an agent needs to invoke it correctly. Only the shape of the returned records is left unaddressed, which is a minor gap.

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%, so both parameters are already documented in the input schema, and the description only restates the query semantics. The limit parameter and its interaction with paging receive no attention beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Search) and resource (HubSpot contacts) plus the matchable fields, which makes it clearly distinct from search_deals by resource alone. It stops short of explicitly contrasting with any sibling, so a 4 rather than a 5.

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?

It conveys the primary context (find a contact by name, email, or company) and the empty-query fallback of returning recently modified contacts. There is no guidance on when to prefer another tool or when this tool is a poor fit.

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

Deploy Server

Other Tools