Skip to main content
Glama

HubSpot MCP Server

by ajaystream

hubspot-update-engagement

Modify HubSpot Notes or Tasks by updating engagement details like content, subject, or status. Requires engagement ID and optional fields for customization, ensuring only specified fields are changed.

Instructions

🛡️ Guardrails: 1. Data Modification Warning: This tool modifies HubSpot data. Only use when the user has explicitly requested to update their CRM. 🎯 Purpose: 1. Updates an existing HubSpot engagement (Note or Task). 2. Allows modification of engagement attributes, content, and metadata. 📋 Prerequisites: 1. You need the engagement ID to update an existing engagement. 2. Use the hubspot-get-engagement tool to get the current engagement details if needed. 3. Use the hubspot-get-user-details tool to get the owner ID. 🧭 Usage Guidance: 1. Use for updating NOTE content or TASK details (subject, description, status). 2. Only include the fields you want to update - other fields will remain unchanged. 3. HubSpot notes and task descriptions support HTML formatting. However headings (<h1>, <h2>, etc.) look ugly in the CRM. So use them sparingly.

Input Schema

NameRequiredDescriptionDefault
associationsYesAssociated records for this engagement
engagementIdYesThe ID of the engagement to update
metadataYesMetadata specific to the engagement type (Note or Task)
ownerIdNoThe ID of the owner of this engagement
timestampNoTimestamp for the engagement (milliseconds since epoch).

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "associations": { "additionalProperties": false, "description": "Associated records for this engagement", "properties": { "companyIds": { "default": [], "items": { "type": "integer" }, "type": "array" }, "contactIds": { "default": [], "items": { "type": "integer" }, "type": "array" }, "dealIds": { "default": [], "items": { "type": "integer" }, "type": "array" }, "ownerIds": { "default": [], "items": { "type": "integer" }, "type": "array" }, "ticketIds": { "default": [], "items": { "type": "integer" }, "type": "array" } }, "type": "object" }, "engagementId": { "description": "The ID of the engagement to update", "exclusiveMinimum": 0, "type": "integer" }, "metadata": { "additionalProperties": true, "description": "Metadata specific to the engagement type (Note or Task)", "properties": {}, "type": "object" }, "ownerId": { "description": "The ID of the owner of this engagement", "exclusiveMinimum": 0, "type": "integer" }, "timestamp": { "description": "Timestamp for the engagement (milliseconds since epoch).", "type": "integer" } }, "required": [ "engagementId", "metadata", "associations" ], "type": "object" }

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/ajaystream/hubspot-mcp-custom'

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