Skip to main content
Glama
amin-ale

HubSpot CRM MCP Server

by amin-ale

crm_batch_create_contacts

Create up to 100 HubSpot contacts in one request and get a detailed outcome for every row, so partial failures never hide unsaved records. Use for bulk loads.

Instructions

Create many HubSpot contacts in one request and report the outcome of every row.

Use this for bulk loads. Use crm_create_contact instead when a retry must not risk duplicates.

Writes, additively. Needs the crm.objects.contacts.write scope. Returns 'succeeded' with the created records and 'failed' with the input index, HubSpot status code, category, message, and original row for every rejection, so a partial failure never hides the rows that did save. This path does not go through the idempotency store: running the same batch twice can create duplicates, so re-send only the rows listed in 'failed'. Cached contact reads are invalidated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactsYesContacts to create, up to 100 per call. Each item is a flat property map such as {'email': 'ada@example.com', 'firstname': 'Ada'}. Keys other than email, firstname, lastname, phone, and company are sent through as custom HubSpot properties.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
failedNoRows HubSpot rejected, with the reason for each.
succeededNoRecords HubSpot created, each with 'id'.
Behavior5/5

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

It discloses the required write scope, the response shape with 'succeeded' and 'failed' arrays, the non-idempotent behavior, and cache invalidation — all beyond the annotations. This gives the agent a full behavioral model.

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 about five sentences, each with a distinct purpose: purpose, usage, behavior, idempotency caveat, cache effect. No fluff.

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?

For a batch mutation tool, it covers permissions, partial failure semantics, retry guidance, and response structure, so the agent can invoke it safely. The output schema is not shown but the description adequately describes the return value.

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?

The schema already describes the contacts array with 100% coverage, and the description adds that failures include the input index and original row, making the parameter's ordering meaningful. It also refers to 'the same batch' which contextualizes the array as a unit.

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 'Create many HubSpot contacts in one request and report the outcome of every row,' which is a specific action and resource. It also contrasts with crm_create_contact by emphasizing 'many... in one request,' making the distinction clear.

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?

It explicitly states 'Use this for bulk loads' and advises using crm_create_contact when a retry must not risk duplicates, giving clear when-to-use and when-not-to-use guidance. No other tool needs that exclusion.

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