Skip to main content
Glama

hubspot_get_contact

Read-onlyIdempotent

Retrieve a single HubSpot contact by its ID, optionally specifying which properties to return.

Instructions

Get a single HubSpot contact by id.

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

Input Schema

NameRequiredDescriptionDefault
contact_idYesHubSpot contact id
propertiesNoComma-separated properties to return
access_tokenYesHubSpot Private App access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds no behavioral context beyond the operation itself—nothing about whether all properties or only default properties are returned, nor anything about property filtering or token scope.

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?

A single short sentence with no filler and the key scope ('by id') front-loaded. It is efficient, though it could have used one additional clause to route agents toward search/list alternatives.

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 simple single-resource read tool with full schema coverage and annotations that already communicate safety and idempotency, the description is nearly complete. The main missing piece is whether the response contains full or filtered property data, but with no output schema a brief return-value note would have helped.

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 the schema already documents contact_id, optional comma-separated properties, and access_token. The description adds no parameter meaning beyond that baseline, so 3 is appropriate.

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 states a specific verb and resource ('Get a single HubSpot contact') and scopes it to lookup by id, which implicitly distinguishes it from hubspot_list_contacts and hubspot_search_contacts. It does not explicitly name those alternatives, so it falls short of 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?

'by id' implies the precondition that you need a known contact id, which gives implied usage guidance. However, it never says when to use this versus search_contacts (find by other attributes) or list_contacts (browse all), and provides no exclusions.

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