HubSpot MCP

objectType

string

The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).

objectType

string

The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).

keywords

array

Optional

Multiple search keywords (max 5) to find relevant properties using efficient keyword-based search. Supports searching for multiple related property concepts in a single request. Examples: - ["urgency"] - Single keyword search - ["assignee", "assigned_to", "owner"] - Multiple related keywords for assignment - ["name", "employees", "zip", "contact"] - Multiple unrelated keywords for different properties If both query and keywords are provided, keywords takes precedence. If empty and no query provided, returns all properties for the object type.

objectType

string

The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).

objectIds

array

Optional

List of object IDs to fetch. Min: 1, Max: 100

objectType

string

The HubSpot CRM object type to operate on (e.g. contacts, companies, deals).

chatInsights

object

Optional

Insights about the chat including user intent and satisfaction level. IMPORTANT: MUST be provided for all scenarios.

filterGroups

array

Optional

* The filter groups that define the search criteria. * Filters that match ALL of several conditions (AND logic) should be put in the same filterGroup. * Filters that match AT LEAST ONE of several conditions (OR logic) should be put in a separate filterGroup.

limit

integer

Optional

Maximum number of results to return per page.

offset

integer

Optional

Pagination offset : number of records to skip before returning results.

properties

array

Optional

List of property names to include in results.

query

string

Optional

Text to search for within the default searchable properties of the specified object type.

feedback

string

User's verbatim feedback about the HubSpot connector. CRITICAL RULES: - Use the user's EXACT words. NEVER paraphrase, summarize, or rewrite. - If the user said it in their language, keep it in their language. - If the user hasn't typed specific feedback yet, do NOT fill this in yourself : ask them first. - Avoid PII : use anonymized references.

explanationOfSatisfaction

string

Optional

Brief explanation of what went wrong from the agent's perspective. When errors occurred: Explain why the agent made a request that failed validation, including what the agent's reasoning was and why it failed. This helps with investigation and improvement. Example: 'Error: "A non-empty list of objects to create or update must be provided" - Agent attempted to batch update contacts but incorrectly passed an empty list because it filtered out all objects based on a misunderstanding of the user's criteria.'

feedbackType

string

Optional

Category of the feedback being submitted. Used to triage and analyze feedback trends. - PROBLEM: Something is broken or not working as expected (errors, incorrect results, bugs). - FEATURE_REQUEST: A request for new functionality or capability, including enhancements to existing features that would require new behavior to be built. - GENERAL_FEEDBACK: Opinions, observations, or suggestions about an existing tool or workflow : e.g., usability impressions, praise, workflow friction, or improvement ideas that don't rise to the level of a bug report or feature request. - OTHER: Use only when the feedback genuinely does not fit any of the above categories.

goal

string

Optional

User's goal or what they were trying to accomplish and relevant conversation context. Avoid PII - use anonymized references. Important: Avoid adding extraneous information, especially from memory.

sourceInterface

string

Optional

Where the feedback originated. - MCP_UI: Submitted from the dedicated in-app feedback UI rendered by the MCP host (e.g. a feedback form/widget the user explicitly opened). - NON_UI: Submitted from a regular chat conversation (no dedicated feedback UI).

action

string

Optional

Defaults to empty, which just checks onboarding status. Set to SET_GOAL to record the user's primary goal : requires goal to also be set.

assetType

string

The asset type name, such as LANDING_PAGE, SITE_PAGE, BLOG_POST, or MEETING_EVENT. If invalid, the error will list valid types.

campaignCrmObjectId

integer

The numeric ID of the campaign to get asset metrics for. Must be greater than 0.

crmObjectIds

array

Optional

Optional list of CRM object IDs to scope metrics to specific assets. When omitted or empty, metrics are returned for all assets of the given assetType associated with the campaign.

endDate

string

Optional

End of the date range in YYYY-MM-DD format.

sql

string

SQL query to execute against HubSpot CRM data.

chatInsights

object

Optional

Insights about the chat including user intent and satisfaction level.

mode

string

Which report mode to run. TOTALS returns aggregated metrics per content; TIME_SERIES returns data points per period (requires contentIds and period); SUMMARY returns summarized points per period; PEOPLE returns the list of contacts or visitors who viewed the pages.

contentIds

array

Optional

Content IDs to filter results to. Numeric for pages and posts; composite string (e.g. hubdb-{tableId}-{rowId}) for HubDB rows. Leave empty to query all pages in the portal. Required for TIME_SERIES and PEOPLE modes.

end

string

Optional

End of the reporting period in YYYY-MM-DD format.

excludedIds

array

Optional

Content IDs to exclude from the result set. Same format as contentIds (numeric or composite string).

includeMetadata

boolean

Optional

TOTALS mode: include per-content metadata (title, URL, type) in the response.

limit

integer

Optional

Maximum number of results to return per page.

offset

integer

Optional

Pagination offset : number of records to skip before returning results.

paginationCursor

string

Optional

Pagination cursor from the previous response to fetch the next page.

peopleType

string

Optional

PEOPLE mode: whether to return CONTACTS (known people) or VISITORS (anonymous). Required for PEOPLE mode.

period

string

Optional

TIME_SERIES or SUMMARY mode: bucket size for the time series. Required for those modes.

scaleByPercent

boolean

Optional

TOTALS mode: scale metric values by their percent contribution to the totals.

search

string

Optional

Free-text search to filter content by title or URL.

sortDirection

string

Optional

TOTALS mode: sort direction. Ignored in other modes.

sortMetric

string

Optional

TOTALS mode: metric to sort by (e.g. rawViews, submissions, contacts). Ignored in other modes.

confirmationStatus

string

Optional

User confirmation for write actions. Must be CONFIRMED or CONFIRMATION_NOT_REQUIRED.

createRequest

object

Optional

Required when creating new CRM objects.

attributionModel

string

Optional

Revenue attribution model for the REVENUE metric. Defaults to LINEAR. See instructions for valid values.

campaignCrmObjectIds

array

Optional

Campaign CRM object IDs to scope the query. Empty for cross-campaign analysis.

dimensions

array

Optional

How to group data (AGGREGATION mode). Max 2 per query. Omit for ungrouped totals. Key mappings: 'channels' or 'content types' (emails, ads, landing pages) -> ASSET_TYPE; specific asset names -> ASSET_TITLE; 'influence types' or 'engagement types' -> INTERACTION_TYPE; traffic/referral source -> INTERACTION_SOURCE; deal names -> DEAL_NAME; deal IDs (for links) -> DEAL.

endDate

string

Optional

End of date range filter (YYYY-MM-DD). Must pair with startDate or both omitted.

filters

array

Optional

Server-side filters on any dimension property. See instructions for examples.

hasReadToolInstructions

boolean

Optional

Set to true if you have already read the usage instructions for get_campaign_attribution_reports (via tool_guidance or a prior error response). If you have not read them yet, leave this unset or set it to false and you will receive an error response containing the full instructions. Not required when polling with taskId.

limit

integer

Optional

Max result rows returned by the server. Defaults to 100, maximum 500. When responseFormat=CONCISE, zero-value rows are filtered client-side after the server applies this limit, so fewer rows than requested may be returned.

metrics

array

Optional

Required: What to measure. REVENUE for attributed revenue (use for any non-deal breakdown like channel/source/asset), DEAL_AMOUNT for per-deal or total deal value (always grouped by deal), DEAL_COUNT for unique deals, CONTACT_COUNT for unique contacts, ATTRIBUTION_COUNT for touchpoint volume.

mode

string

Optional

Report mode. Only AGGREGATION is currently supported.

responseFormat

string

Optional

Controls response verbosity. CONCISE (default) omits zero-value metric entries and drops rows where all metrics are zero, reducing token usage. DETAILED returns all rows and fields including zero values.

sortByMetric

string

Optional

Sort results by this metric (DESC by default). Use to rank rows without post-processing, e.g. REVENUE returns highest-revenue rows first.

sortOrder

string

Optional

Sort direction for sortByMetric. ASC or DESC. Defaults to DESC.

startDate

string

Optional

Start of date range filter (YYYY-MM-DD). Must pair with endDate or both omitted. Filters by deal close date for REVENUE/DEAL_AMOUNT, deal create date for DEAL_COUNT, touchpoint timestamp for CONTACT_COUNT/ATTRIBUTION_COUNT.

operation

string

Required. The operation to perform: GET_ANALYTICS, GET_ASSET_METRICS, or GET_CONTACTS.

analyticsRequest

object

Optional

Analytics request data. Required when operation is GET_ANALYTICS.

assetMetricsRequest

object

Optional

Asset metrics request data. Required when operation is GET_ASSET_METRICS.

campaignCrmObjectId

integer

The numeric object ID of the campaign. Must be greater than 0.

contactType

string

The contact attribution type: NEW_CONTACTS_FIRST_TOUCH (first marketing interaction was this campaign), NEW_CONTACTS_LAST_TOUCH (last interaction before conversion), or INFLUENCED_CONTACTS (any engagement within the date range).

endDate

string

Optional

End of the date range in YYYY-MM-DD format.

limit

integer

Optional

Maximum number of results to return per page.

offset

integer

Optional

Pagination offset : number of records to skip before returning results.

action

string

Action to perform. One per call. READ actions (no side effects): "MODULES": list every module on the page draft. Each entry includes the module's field values, its layout position (sectionId, rowIndex, parentCellName when it lives inside a nested column, and cellWidth/cellX on the 12-column grid), and ownership flags (overrideable, globalOwned, globalPartialPath, themePartialOwned). Positions are populated even on a freshly created template page, before any edit. Capture a module's position here BEFORE you REMOVE or MOVE it so you can restore or reposition it precisely. Check ownership before REMOVE/MOVE: true global partials (header/footer) and global widgets are refused, but modules inside theme dnd_partial sections are removable and movable. "MODULE_TYPES": list available module types for this page's theme (call before INSERT). "MODULE_DEF": full field schema for a module type (requires modulePath). The response also includes the curated guide in moduleGuide when one exists, so a separate MODULE_GUIDE call is usually unnecessary. "MODULE_STYLES": read the layout styles (padding, margin, background, visibility) for a module (requires moduleId). "MODULE_GUIDE": (rarely needed : MODULE_DEF already returns the same guide inline) curated markdown for the modulePath covering required fields, common traps, and a minimal INSERT body. Errors if no guide exists; check MODULE_TYPES.hasGuide first. "REVISIONS": list recent page revisions for undo. "TEMPLATES": list landing page templates available in the portal (contentId not required). "FORMS": list forms available in the portal for embedding via the @hubspot/form module (contentId not required). Returns guid, name, portalId, formType, isPublished, createdAt, updatedAt. "BRAND_KIT": fetch the portal's primary brand kit (colors, fonts, logos) when brand-consistent content would help : e.g. picking a CTA color, a hero font, or a logo to drop into a header (contentId not required). WRITE actions (mutate the same shared draft : issue them ONE AT A TIME, never in parallel): "CLONE": duplicate an existing page (requires contentId of the source page; optional pageName and slug for the clone). Returns a new contentId. "CREATE_FROM_TEMPLATE": create the page from a template (requires pageName and templatePath; optional slug). MUST be preceded by a proposal card (call render_landing_page_ui directly with a "propose" target : there is no separate write step to propose) and an explicit user confirmation IN CHAT : never the first step of creating a page, and choosing a template is NOT confirmation. Returns contentId. "SET_MODULE_FIELDS": verbatim field patch on one module (requires contentId, moduleId, fieldOverridesJson). "SET_MODULE_STYLES": set layout styles (padding, margin, background, visibility) on one module (requires contentId, moduleId, stylesJson). Merge semantics : only supplied fields are updated. Call action=MODULE_STYLES first to see current values. "SET_SECTION_STYLES": set the background, padding, margin, or full-width of the ENTIRE SECTION band a module sits in (requires contentId, moduleId, stylesJson; moduleId is any module inside the band, used as an anchor). This is the correct way to do "make this section's background " : do NOT inject CSS via SET_METADATA headHtml for section backgrounds. Merge semantics. Page-scoped bands : including theme dnd_partial sections : CAN be styled; only true global sections (header/footer/global widgets) are refused. "INSERT": add a new module (requires contentId, modulePath; then EITHER anchorModuleId+anchorPosition for anchor-based placement, OR sectionId+rowStart+columnStart+columnsSpanned for grid-coord placement; optional fieldOverridesJson). "REMOVE": delete one module (requires contentId, moduleId). If it was the last module in its section band, the now-empty band : background and padding included : is collapsed too, so no empty "Drop modules here" ghost band is left behind. "REMOVE_SECTION": delete the ENTIRE section band a module sits in : the whole top-level row, every module in it, AND the band's own background/padding styles (requires contentId, moduleId; moduleId is any module inside the target band, used as an anchor). Page-scoped sections : including theme dnd_partial sections like a logo bar : CAN be removed; only true global sections are refused. "MOVE": reposition module (requires contentId, moduleId; optional sectionId, rowStart, columnStart). "SET_METADATA": update page metadata : pageName, htmlTitle, slug, metaDescription, featuredImageUrl, language, headHtml (requires contentId; all metadata fields optional). "PUBLISH": publish draft (requires contentId; confirm with the user first). "RESTORE_REVISION": roll back to revision (requires contentId, revisionId; confirm first).

anchorModuleId

string

Optional

Anchor-based placement: moduleId of an existing module that the new INSERT should land relative to. When provided, omit rowStart / columnStart / columnsSpanned : the backend resolves the target row from the anchor and auto-redistributes column widths across siblings. Pair with anchorPosition.

anchorPosition

string

Optional

Anchor placement direction. Used with anchorModuleId on INSERT. Values: "BEFORE" (new module on a new row immediately above the anchor's row), "AFTER" (new row immediately below), "IN_ROW_WITH" (sibling cell appended to the right of all existing cells in the anchor's row : siblings give up width), "IN_ROW_BEFORE" (sibling cell positioned to the LEFT of the anchor within the same row), "IN_ROW_AFTER" (sibling cell positioned to the RIGHT of the anchor within the same row, regardless of any cells beyond the anchor), "START_OF_SECTION" (first row of anchor's section), "END_OF_SECTION" (last row of anchor's section), "STACK_ABOVE" (wrap the anchor in a column and place the new module ABOVE it as a stacked row), "STACK_BELOW" (same, stacked BELOW). STACK_* builds a "unified section" : both modules share ONE wrapper cell as separate rows (the shape the editor's drag-to-stack creates); use it instead of BEFORE/AFTER when the two modules should read as one visual group rather than independent section rows. STACK requires a module anchor inside a section (not a top-level section id).

availableForNewContent

boolean

Optional

When action=TEMPLATES: filter to templates available for new page creation. Omit to return all templates.

columnsSpanned

integer

Optional

Width in columns on the 12-column grid. Required for INSERT when using legacy grid-coord placement. Full width=12, two halves=6 each, three thirds=4 each. Omit when using anchor-based placement (anchorModuleId + anchorPosition) : width is computed automatically by stealing from siblings.

columnStart

integer

Optional

1-based column position on a 12-column grid. Required for INSERT (grid-coord placement). Optional for MOVE. columnStart=1 is leftmost.

contentId

integer

Optional

Content ID of the landing page. Required for most actions. NOT required for CREATE_FROM_TEMPLATE (creates a new page), TEMPLATES, FORMS, BRAND_KIT, MODULE_DEF, and MODULE_GUIDE.

featuredImageUrl

string

Optional

Featured image URL for social sharing. Only used for SET_METADATA. Omit to leave unchanged.

fieldOverridesJson

string

Optional

JSON object of verbatim field values (e.g. {"heading":"Close deals faster"}). Required for SET_MODULE_FIELDS. Optional for INSERT (sets initial field values on the new module).

folderName

string

Optional

When action=TEMPLATES: filter by folder name (e.g. "my-theme/templates").

headHtml

string

Optional

Raw HTML injected into (e.g. ""). Only used for SET_METADATA. Omit to leave unchanged.

htmlTitle

string

Optional

HTML