Skip to main content
Glama
nubiia-dev

@iamsamuelfraga/mcp-hubspot

by nubiia-dev

hubspot_properties_create

Create a custom property on HubSpot CRM objects like deals or contacts to store business-specific data. Supports text, numbers, dates, dropdowns, and more.

Instructions

Create a new custom property (field) on a HubSpot CRM object type. Use this to extend deal, contact, company, or other object records with business-specific data fields.

Common type+fieldType combinations: Single-line text: type="string", fieldType="text" Multi-line text: type="string", fieldType="textarea" Number: type="number", fieldType="number" Date: type="date", fieldType="date" Dropdown: type="enumeration", fieldType="select" (requires options) Checkbox list: type="enumeration", fieldType="checkbox" (requires options) Yes/No toggle: type="bool", fieldType="booleancheckbox"

Note: property names must be lowercase with underscores (e.g., "my_custom_field"). The name cannot be changed after creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesInternal property name (lowercase letters, numbers, underscores only). Used as the key when reading/writing this field. Cannot be changed after creation.
typeYesData type. Common values: "string", "number", "date", "datetime", "enumeration", "bool".
labelYesDisplay label shown in HubSpot UI and reports
hiddenNoWhether to hide this property in the UI
optionsNoRequired when type="enumeration". Array of selectable options, each with a unique value.
fieldTypeYesUI rendering type. Must be compatible with the chosen "type" field. See tool description for common combinations.
formFieldNoWhether this property can be used in HubSpot forms
groupNameYesProperty group this field belongs to (e.g., "dealinformation", "contactinformation")
objectTypeYesCRM object type to add the property to (e.g., "contacts", "deals", "companies")
descriptionNoOptional description explaining the purpose of this property
displayOrderNoPosition of this property in forms and records (lower = earlier)
hasUniqueValueNoWhether values must be unique across all records of this type. Useful for external IDs.
Behavior4/5

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

No annotations provided. The description discloses important behaviors: naming constraints (lowercase underscores) and that name is immutable after creation. It lists common type/fieldType combinations.

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 concise with a main sentence, a helpful table of common combinations, and a key note, all front-loaded with no wasted words.

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

Completeness4/5

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

Given 12 parameters (6 required) and no output schema, the description covers the creation intent, parameter combinations, and naming rules. However, it could mention return value or error conditions.

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 coverage is 100% with descriptions for all 12 parameters. The description adds value beyond the schema by explaining common type+fieldType combinations and naming convention.

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 clearly states it creates a new custom property on a HubSpot CRM object type, and distinguishes from siblings like hubspot_properties_get/list by specifying the create action.

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 says 'Use this to extend deal, contact, company, or other object records' which indicates when to use, but doesn't explicitly state when not to use or suggest alternatives.

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/nubiia-dev/mcp-hubspot'

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