Skip to main content
Glama

hubspot_get_contact

Retrieve specific contact details from HubSpot CRM using a contact ID to access customer information and properties for sales analysis.

Instructions

Get a specific contact by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactIdYesThe ID of the contact to retrieve
propertiesNoList of properties to include in the results

Implementation Reference

  • Core implementation of the tool logic: retrieves a specific contact by ID from HubSpot CRM using the API client.
    async getContact(contactId: string, properties?: string[]): Promise<any> {
      return await this.client.crm.contacts.basicApi.getById(contactId, properties || ["email", "firstname", "lastname", "phone"]);
    }
  • Tool definition including name, description, and input schema validation for 'hubspot_get_contact'.
    const getContactTool: Tool = {
      name: "hubspot_get_contact",
      description: "Get a specific contact by ID",
      inputSchema: {
        type: "object",
        properties: {
          contactId: {
            type: "string",
            description: "The ID of the contact to retrieve",
          },
          properties: {
            type: "array",
            items: {
              type: "string",
            },
            description: "List of properties to include in the results",
          },
        },
        required: ["contactId"],
      },
    };
  • Request handler case that parses arguments, validates input, calls the core getContact method, and formats the response for MCP.
    case "hubspot_get_contact": {
      const args = request.params.arguments as unknown as GetContactArgs;
      if (!args.contactId) {
        throw new Error("Missing required argument: contactId");
      }
      const response = await hubspotClient.getContact(args.contactId, args.properties);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • index.ts:1706-1727 (registration)
    Registers the 'hubspot_get_contact' tool (as getContactTool) in the list returned by ListToolsRequest handler.
      return {
        tools: [
          searchContactsTool,
          getContactTool,
          createContactTool,
          updateContactTool,
          listDealsTool,
          getDealTool,
          createDealTool,
          updateDealTool,
          listCompaniesTool,
          getCompanyTool,
          getSalesAnalyticsTool,
          getDealHistoryTool,
          getDealNotesTool,
          getEngagementsByDealTool,
          getSalesPerformanceTool,
          getPipelineAnalyticsTool,
          getForecastAnalyticsTool,
        ],
      };
    });
  • TypeScript interface defining the expected input arguments for the hubspot_get_contact tool.
    interface GetContactArgs {
      contactId: string;
      properties?: string[];
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the basic operation without mentioning authentication requirements, rate limits, error conditions, or what happens if the contact doesn't exist. For a read operation with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple retrieval tool.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what data is returned, error handling, or behavioral constraints. Given the complexity of interacting with a CRM system and the lack of structured metadata, more context is needed.

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 both parameters thoroughly. The description doesn't add any additional meaning about the parameters beyond what's in the schema (e.g., format of contactId, examples of properties). This meets the baseline for high schema coverage.

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 clearly states the verb ('Get') and resource ('a specific contact by ID'), making the purpose immediately understandable. It distinguishes from list/search operations but doesn't explicitly differentiate from other get operations like hubspot_get_company or hubspot_get_deal, which is why it doesn't reach a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like hubspot_search_contacts or hubspot_list_companies. It doesn't mention prerequisites (e.g., needing a contact ID) or compare it to sibling tools, leaving the agent to infer usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scopiousdigital/hubspot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server