Skip to main content
Glama
amin-ale

HubSpot CRM MCP Server

by amin-ale

crm_create_contact

Idempotent

Creates a single HubSpot contact from supplied properties and returns the new record. Prevents duplicate contacts on retry with an idempotency key.

Instructions

Create one HubSpot contact from the properties given and return the new record.

Use this for single creates, especially ones a retry might repeat. Use crm_batch_create_contacts to load many rows at once, and crm_update_contact to change a record that already exists.

Writes, additively. Needs the crm.objects.contacts.write scope. The call is keyed by 'idempotency_key', or by a hash of the properties when none is given, and a repeat of the same key replays the stored record instead of creating a second one. That key store lives in this process, so it covers retries within a session and not restarts. Cached contact reads are invalidated. At least one property must be supplied or the call fails validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoPrimary email address. HubSpot deduplicates contacts on this value.
phoneNoPhone number in any format HubSpot accepts, e.g. '+1-202-555-0101'.
companyNoCompany name stored on the contact. This is a text property, not an association to a company record.
lastnameNoFamily name. HubSpot property 'lastname'.
firstnameNoGiven name. HubSpot property 'firstname'.
idempotency_keyNoCaller-chosen key that makes a retry replay the first result instead of creating a second record. Omit to derive one from the properties.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesHubSpot record id, stable for the life of the record.
archivedNoTrue when the record is archived (soft-deleted).
propertiesNoProperty values HubSpot returned for the requested property set.
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses the required OAuth scope, the session-scoped idempotency store, cache invalidation on writes, and the validation requirement of at least one property. No contradiction with annotations; it meaningfully enriches them.

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?

Three tight paragraphs: purpose, usage guidance, and behavioral details. Every sentence carries information, with no filler or repetition of the schema. Front-loaded with the core purpose.

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?

With an output schema present, the description appropriately avoids re-explaining return values. It covers authentication, idempotency semantics, cache effects, and validation constraints, making it sufficient for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds valuable semantic context beyond the schema: the 'at least one property' validation rule and the idempotency key derivation/replay behavior. This justifies a 4.

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 opens with a specific verb and resource: 'Create one HubSpot contact from the properties given and return the new record.' It explicitly contrasts with sibling tools like crm_batch_create_contacts and crm_update_contact, making the tool's unique role unambiguous.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'Use this for single creates, especially ones a retry might repeat.' It also names alternatives: crm_batch_create_contacts for bulk loading and crm_update_contact for existing records, giving clear decision criteria.

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/amin-ale/hubspot-mcp-server'

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