Skip to main content
Glama
tillheidrich

hubspot-mcp-server

by tillheidrich

create_form

Create a live HubSpot form with custom fields, submit button, and success message. Use it to add a submittable form to your page after review.

Instructions

Create a HubSpot form.

NOT a draft. HubSpot's v3 Forms API has no draft state, so this form is live and submittable the moment it is created. What keeps it inert is that it is not embedded anywhere — you place it on a page yourself once you have reviewed it. Say this to the user when you create one.

Args: name: form name shown in the HubSpot listing. fields: list of simplified field specs, in display order. Each entry: { "name": "firstname", # required: contact property internal name "label": "First name", "type": "single_line_text", # see below "required": true, "hidden": false, "options": ["A", "B"], # required for dropdown/radio/checkbox "placeholder": "...", "description": "..." } Types: single_line_text, multi_line_text, email, phone, number, dropdown, radio, checkbox, single_checkbox, date, file. submit_button_text: label on the submit button. success_message: message shown after a successful submission. language: ISO 639-1 code. Default 'en'.

Note on consent: GDPR consent options are not set here, because they need a lawful basis and subscription type IDs that vary per portal. Configure consent in the HubSpot form editor after creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
fieldsYes
languageNoen
success_messageNoThanks — we'll be in touch.
submit_button_textNoSubmit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses key side effects: immediate liveness, non-embedding, and lack of consent settings. It stops short of covering error conditions, rate limits, or auth requirements, but for a create operation the most critical behaviors are transparently stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is lengthy but every section serves a purpose—the live/draft distinction, the parameter documentation, and the consent caveat. It is structured with an Args block that aids scanning. It could be trimmed slightly, but the density is justified given the tool's complexity.

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?

The description covers all five parameters, the behavioral implications, and the consent gap. An output schema exists, so return format need not be detailed. For a create tool with a nested fields structure, this is fully sufficient for correct invocation.

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

Parameters5/5

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

Schema coverage is 0%, so the description is the sole source of parameter meaning. It provides exhaustive documentation: a detailed field spec with types, examples, required fields, and per-type notes; descriptions for all other parameters; and a note about consent that explains why it's omitted. This fully compensates for the schema's emptiness.

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 states a clear verb and resource ('Create a HubSpot form') and immediately distinguishes it from draft-based tools by emphasizing it is not a draft and becomes live instantly. This differentiates it from sibling create_*_draft tools and clarifies its unique nature.

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

Usage Guidelines4/5

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

The description gives strong usage context: it explains the form is live but not embedded, instructs the agent to tell the user this, and notes that consent must be configured separately. It does not explicitly name alternative tools, but the draft distinction and consent guidance make the intended usage clear.

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