Skip to main content
Glama

hubspot_create_contact

Create new contacts in HubSpot CRM by providing email address and contact details to build your customer database and manage relationships.

Instructions

Create a new contact in HubSpot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertiesYesContact properties

Implementation Reference

  • MCP tool handler that validates input, calls HubSpotClient.createContact, and returns the JSON response.
    case "hubspot_create_contact": {
      const args = request.params.arguments as unknown as CreateContactArgs;
      if (!args.properties || !args.properties.email) {
        throw new Error("Missing required arguments: properties including email");
      }
      const response = await hubspotClient.createContact(args.properties);
      return {
        content: [{ type: "text", text: JSON.stringify(response) }],
      };
    }
  • Tool definition with input schema requiring 'properties' object containing at least 'email', used for validation and documentation.
    const createContactTool: Tool = {
      name: "hubspot_create_contact",
      description: "Create a new contact in HubSpot",
      inputSchema: {
        type: "object",
        properties: {
          properties: {
            type: "object",
            properties: {
              email: {
                type: "string",
                description: "Contact's email address",
              },
              firstname: {
                type: "string",
                description: "Contact's first name",
              },
              lastname: {
                type: "string",
                description: "Contact's last name",
              },
            },
            required: ["email"],
            additionalProperties: true,
            description: "Contact properties",
          },
        },
        required: ["properties"],
      },
    };
  • Core helper method in HubSpotClient that wraps the HubSpot API call to crm.contacts.basicApi.create.
    async createContact(properties: { [key: string]: any }): Promise<any> {
      const contactInput = {
        properties,
      };
      return await this.client.crm.contacts.basicApi.create(contactInput);
    }
  • index.ts:1707-1725 (registration)
    Registration of the tool in the listTools handler by including createContactTool in the returned tools array.
    tools: [
      searchContactsTool,
      getContactTool,
      createContactTool,
      updateContactTool,
      listDealsTool,
      getDealTool,
      createDealTool,
      updateDealTool,
      listCompaniesTool,
      getCompanyTool,
      getSalesAnalyticsTool,
      getDealHistoryTool,
      getDealNotesTool,
      getEngagementsByDealTool,
      getSalesPerformanceTool,
      getPipelineAnalyticsTool,
      getForecastAnalyticsTool,
    ],
  • TypeScript interface defining the expected arguments for the create contact tool.
    interface CreateContactArgs {
      properties: {
        email: string;
        firstname?: string;
        lastname?: string;
        [key: string]: any;
      };
    }
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. 'Create a new contact' implies a write operation but doesn't specify permissions required, whether duplicates are handled, what happens on failure, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 maximally concise - a single sentence that states the core purpose without any wasted words. It's front-loaded with the essential information and contains no unnecessary elaboration or redundant phrasing.

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 creation/mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address what happens after creation (success/failure responses), how to handle duplicate emails, what permissions are needed, or what distinguishes this from update operations. The combination of mutation behavior and missing structured documentation requires more descriptive context.

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?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage. The schema fully documents the single 'properties' parameter with its nested structure and required 'email' field. The baseline score of 3 reflects adequate parameter documentation coming entirely from the schema, with no additional value from the description.

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 action ('Create') and resource ('new contact in HubSpot'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'hubspot_update_contact' beyond the basic verb difference, nor does it specify what distinguishes it from other creation tools like 'hubspot_create_deal'.

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. It doesn't mention when to choose this over 'hubspot_update_contact' for existing contacts, or how it relates to sibling tools like 'hubspot_search_contacts' or 'hubspot_get_contact'. There's no context about prerequisites, constraints, or typical use cases.

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