Skip to main content
Glama
Sign In
HubSpot MCP Server

HubSpot MCP Server

by djmoore-projects
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hubspot_get_contact

Retrieve a contact's first name, last name, lifecycle stage, and company name from HubSpot using their email address.

Instructions

Look up a HubSpot contact by email address. Returns first name, last name, lifecycle stage, and associated company name.

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

Input Schema

NameRequiredDescriptionDefault
emailYesThe contact's email address to search for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description should fully disclose behavior. It only lists returned fields, omitting error handling, idempotency, or side effects. Missing transparency on what happens if email is not found.

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 concise sentences front-load the core action and return fields, with no redundant or extraneous content.

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?

Description covers purpose and return fields but lacks output schema and details on error behavior or edge cases. Adequate for a simple lookup but incomplete for robust agent use.

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 describes the email parameter. The description's phrase 'by email address' is redundant. No additional semantics beyond schema are provided.

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 uses specific verb 'Look up' and resource 'HubSpot contact by email address', clearly distinguishing from sibling tools like hubspot_create_contact (create) and hubspot_search_companies (search).

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 when/when-not-to-use guidance is provided. The context implies usage when needing contact details by email, but does not mention alternatives or exclusions like creating contacts.

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