Skip to main content
Glama

Hubspot

by io.github.pipeworx-io

Hs Get Contact

hs_get_contact
Read-onlyIdempotent

Fetch a contact's full profile by ID. Returns name, email, phone, company, and all custom properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesHubSpot contact ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoContact ID
archivedNoWhether contact is archived
createdAtNoCreation timestamp
updatedAtNoLast update timestamp
propertiesNoContact properties (name, email, phone, company, custom fields)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "description": "Whether contact is archived",
+      "type": "boolean"
+    },
+    "createdAt": {
+      "description": "Creation timestamp",
+      "type": "string"
+    },
+    "id": {
+      "description": "Contact ID",
+      "type": "string"
+    },
+    "properties": {
+      "description": "Contact properties (name, email, phone, company, custom fields)",
+      "type": "object"
+    },
+    "updatedAt": {
+      "description": "Last update timestamp",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "12345"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. Description adds context about returning all custom properties, which complements annotations. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single front-loaded sentence containing all essential information (action, resource, output) with no wasted words.

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?

Simple tool with one parameter, full schema coverage, rich annotations, and presence of output schema. Description fully covers necessary context for a single-entity fetch operation.

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% with clear schema description for 'id'. Description simply says 'by ID', adding no extra meaning beyond the schema. Baseline 3 applies.

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 uses specific verb 'Fetch' and resource 'contact's full profile', lists returned fields (name, email, phone, company, all custom properties). Clearly distinguishes from siblings like hs_list_contacts (bulk list) and hs_search_contacts (search by criteria).

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?

Description implies usage via ID but provides no explicit guidance on when to use this tool versus alternatives (e.g., hs_search_contacts, hs_list_contacts). Does not state exclusions or prerequisites.

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

All Hubspot toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools are near-duplicates or overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve overlapping query/discovery purposes. The polymarket tools and HubSpot tools are more distinct, but the set as a whole has fuzzy boundaries between many members.

Naming Consistency2/5

Naming is inconsistent across the set: HubSpot tools use an hs_ prefix, Pipeworx tools mostly use bare verbs (ask_pipeworx, recall, forget), and other tools mix styles (ai_visibility_check, generate_llms_txt, polymarket_edges). The hs_* subset is consistent, but overall there is no single predictable pattern.

Tool Count2/5

38 tools is too many for the apparent scope, especially since the server is named 'Hubspot' but only 6 of the tools are HubSpot-specific. A large portion of the catalog covers unrelated Pipeworx data access, prediction markets, memory, and npm scanning, making the set feel bloated and unfocused.

Completeness2/5

The HubSpot portion of the tool set is read-only: it can get, list, and search companies/contacts/deals, but has no create, update, or delete operations, leaving obvious lifecycle gaps. If the intended domain is actually Pipeworx/data research, the HubSpot tools seem like an unrelated afterthought, so the surface is incomplete for either interpretation.

Resources