discover_hubspot_schema
ChatGPTDiscovers HubSpot data types, pipelines, and stages. <capabilities> - Searches across all HubSpot data types available to the current user - Returns type names that can be used as input to other tools - Shows read/write access status for each type based on the current user's permissions - Returns pipelines and their stages (including open/closed status) for a data type </capabilities> <usage_guidance> - Use this tool FIRST when you need to identify which data types exist before querying data - Use SEARCH_OBJECT_TYPES when you don't know the exact type name - Use GET_OBJECT_TYPES when you already know the type names (e.g. CONTACT, DEAL), or with an empty typeNameFilter list to retrieve all available types - Use GET_PIPELINES to list the pipelines and stages for a type (e.g. deal or ticket stages) - GET_PIPELINES stage metadata: probability (DEAL only) is the likelihood (0-1) the deal closes successfully. state (all other types) is OPEN or CLOSED, except for LEAD where the values are NEW, IN_PROGRESS, QUALIFIED, or UNQUALIFIED — QUALIFIED and UNQUALIFIED are the closed/terminal states, NEW and IN_PROGRESS are open - Check readAccess/writeAccess before attempting operations on a type </usage_guidance> <examples> <example> <user_input>How many support requests did we get last month?</user_input> <tool_call>{"query": {"_queryType": "SEARCH_OBJECT_TYPES", "searchTerms": "support requests tickets"}}</tool_call> </example> <example> <user_input>How many products do we have?</user_input> <thoughts>"products" is ambiguous — it may be HubSpot's standard Products object or a custom object like p12345_product_models, and semantic search tends to rank the standard one first, so I won't just take the top hit. I'll review all candidates and, if more than one plausibly matches, ask the user to clarify before querying.</thoughts> <tool_call>{"query": {"_queryType": "SEARCH_OBJECT_TYPES", "searchTerms": "products"}}</tool_call> </example> <example> <user_input>What fields are on contacts and deals?</user_input> <tool_call>{"query": {"_queryType": "GET_OBJECT_TYPES", "typeNameFilter": ["CONTACT", "DEAL"]}}</tool_call> </example> <example> <user_input>What types of data does HubSpot have?</user_input> <tool_call>{"query": {"_queryType": "GET_OBJECT_TYPES"}}</tool_call> </example> <example> <user_input>What are the deal pipeline stages?</user_input> <tool_call>{"query": {"_queryType": "GET_PIPELINES", "objectType": "DEAL"}}</tool_call> </example> </examples>
get_aeo_metrics
ChatGPTPortal-level AEO analytics: brand visibility, mentions, citations, competitor share-of-voice, and per-assistant breakdowns for a date window. Select the sections you need with include, a JSON array of section names, e.g. ["SUMMARY", "PROMPTS"] (SUMMARY, PROMPTS, CITATIONS, CITATION_ANALYSIS, COMPETITORS, ASSISTANT_BREAKDOWN, RUN_STATUS, ICPS_AND_PRODUCTS, BUSINESS_UNITS, LIMITS); defaults to {SUMMARY, RUN_STATUS}. businessUnitId is optional: omit it to use the portal's business unit automatically, or call once with include=["BUSINESS_UNITS"] first to choose one when the portal has several. CITATION_ANALYSIS additionally requires a citationUrl. Dates are ISO-8601 (YYYY-MM-DD); default to the last 30 days. Call tool_guidance (mcpToolInstructions) for the full section catalog, setup-status semantics, and field-level details.
get_campaign_analytics
ChatGPTGet campaign analytics (METRICS or REVENUE_ATTRIBUTION) for one or more campaigns. Each entry in the request list is a full analytics request. Each response contains the campaignObjectId of the requested campaign.
get_campaign_asset_metrics
ChatGPTGet metrics for specific CRM objects associated with a campaign. campaignObjectId, assetType, and crmObjectIds are all required. Search the campaign's associated objects for objects of the given asset type to retrieve their CRM object IDs, then pass those IDs here. assetType should be a valid campaign asset type such as LANDING_PAGE, SITE_PAGE, BLOG_POST, or MEETING_EVENT. If an invalid assetType is provided, the error will list the valid types. Optional date range (ISO 8601 YYYY-MM-DD) to populate date range metrics.
get_campaign_attribution_reports
ChatGPTREQUIRED FIRST STEP: before your first call, invoke tool_guidance for "get_campaign_attribution_reports" and follow it. The dimension names, filter syntax, date-range semantics, grouping rules, and query patterns live in tool_guidance, not in this description; calling this tool without them produces wrong or failed queries. If you skip tool_guidance, submit your first call with hasReadToolInstructions=false (the default); the tool will return status=READ_TOOL_INSTRUCTION_REQUIRED with the full instructions in toolInstructions — read them, then retry with hasReadToolInstructions=true. Revenue ranking: dimensions=[CAMPAIGN], metrics=[REVENUE], sortByMetric=REVENUE. Attribution data tool: all metrics (revenue, deal amounts, deal counts, contact counts) are scoped to the closed-won deal attribution pipeline. Use for revenue, attributed deal, and attributed contact questions. CONTACT_COUNT = contacts whose interactions influenced closed-won deals; this is NOT a "new contacts generated" metric. For non-attribution contact queries (new contacts, influenced contacts, sessions), use read_campaign_data with GET_ANALYTICS. TOP/BEST PERFORMING ASSET: use dimension=ASSET_TITLE; set sortByMetric to the metric the question asks about (REVENUE when unspecified, DEAL_COUNT for "most deals", DEAL_AMOUNT for "highest deal value", CONTACT_COUNT for "most contacts", ATTRIBUTION_COUNT for "most interactions"). Attribution metrics share a common unit across all asset types. Do NOT rank by calling getCampaignAssetMetrics per type — those engagement metrics (views vs. open rate) are not cross-type comparable. Scope note: this data covers closed-won / attributed deals only. For deals at any stage (open, opportunity, qualifiedtobuy, and so on), use read_campaign_data with operation=GET_ASSET_METRICS and assetType=DEAL (returns name, stage, amount, close date for all associated deals) or search_crm_objects with a campaign association filter. For long-running queries, this returns a PROCESSING status with a taskId to poll for results.
get_campaign_contacts_by_type
ChatGPTGet paginated contact IDs for a campaign filtered by attribution type. contactType options: NEW_CONTACTS_FIRST_TOUCH (first marketing interaction was this campaign), NEW_CONTACTS_LAST_TOUCH (last interaction before conversion), INFLUENCED_CONTACTS (any engagement within the date range). Returns contact VIDs usable with CRM tools. Date range is optional (ISO 8601 YYYY-MM-DD); omit for full campaign lifetime. Pagination: offset-based, limit 100–500.
get_content_analytics_report
ChatGPTRun a content analytics report across landing pages, website pages, and blog posts in the portal. Returns: TOTALS: ranked rows of contentId, contentTitle, and the requested metric value. TIME_SERIES: per-contentId series of {timestamp, value} points for the requested metric and period. SUMMARY: aggregated per-period points (one value per bucket) for the requested metric. PEOPLE: list of contacts/visitors (contactId or session identifier, plus available identity fields) who viewed the specified contentIds. Pick mode by intent: TOTALS to rank, TIME_SERIES to chart trends per page, SUMMARY for a single aggregated trend, PEOPLE for who-viewed lookups. TIME_SERIES/PEOPLE require contentIds. Examples: mode=TOTALS metric=VIEWS limit=10 -> top 10 pages by views. mode=TIME_SERIES contentIds=[123] metric=SUBMISSIONS period=LAST_30_DAYS -> daily submissions for page 123. Requires 'Read analytics related to pages, blogs and other content assets' permission and a Pro or Enterprise portal.
get_conversation_channel_metadata
ChatGPTList inboxes, channels, and channel instances in this portal. Call before filtering search_conversations by channel/inbox/instance — do not guess IDs. Use channelId for a channel-type filter and channelInstanceId for a specific configured instance.
get_crm_objects
ChatGPTFetches multiple CRM objects of the same object type in a single request. <returns> A list of CRM objects with their properties, identified by their unique IDs, containing: - id: Unique identifier for the CRM object - properties: Key-value pairs of property names and their values - createdAt: Timestamp when the object was created - updatedAt: Timestamp when the object was last updated - url: URL to view the object in HubSpot </returns> <usage_guidance> - Use the search_crm_objects tool to list a few objects first without a filter criteria - Then use the get_crm_objects tool to retrieve those objects by their IDs without any properties in the tool input to understand the data model - This will help you understand the structure of the objects and their properties </usage_guidance>
get_home_page_data
ChatGPT<purpose>Reads the user's HubSpot home feed for the HubSpot home app.</purpose><usage_guidance>Only the HubSpot home app calls this tool. Don't call it yourself.</usage_guidance>
get_marketing_email_analytics
ChatGPTProvides analytics data for marketing emails based on sends in the given date range. To find emails created or published within certain date ranges, use search_crm_objects instead. The request takes a single field, analysisRequest, which is an OBJECT — never a bare string. It carries a "_type" discriminator plus the section settings for that type. Available analysisRequest types (set as analysisRequest._type): - "OVERVIEW" — portal-level aggregate statistics (sends, deliveries, opens, clicks, bounces, unsubscribes) over a date range, optionally scoped to specific emails or broken down by time interval. Uses statisticsSection. - "HEALTH" — portal email health diagnostics. Four sections: mxGroupStatisticsSection (delivery performance statistics by the destination domains with the most deliveries, over a date range); healthScoresSection (monthly 0–100 health scores with per-metric breakdown for click, open, hard bounce, spam report, unsubscribe, and click-to-open — up to 6 months, GLOBAL or INDUSTRY benchmark); sourceHealthScoresSection (same per-metric breakdown per contact source, i.e. where contacts were imported from, past ~30 days); bounceReasonsSection (breakdown of bounces by reason category over a date range, split into hard and soft bounces, optionally scoped to a single MX group). - "RECIPIENTS" — delivery outcome and engagement summary for a specific contact recipient, with an optional ordered event timeline (sent, opened, clicked, bounced, etc.). Uses recipientDetailsSection. No operation returns a collection of all recipients for an email; only individual recipient information is available. - "UNSUBSCRIBE_SURVEY" — breakdown of unsubscribe survey responses by reason code (NO_LONGER_INTERESTED, DID_NOT_SIGN_UP, TOO_MANY_EMAILS, IRRELEVANT_CONTENT, OTHER) over a date range. Optionally scoped to a specific email by emailContentId. Use this to understand WHY contacts unsubscribed and improve future emails.
get_organization_details
ChatGPTLists organization-wide teams, job titles (roles), seats, and account information (eg timezone, currency). Use the include parameter to request only the data you need. <returns> - GUIDANCE (optional): Returned if additional context is required so provide a useful response Only fields listed in the include parameter are returned (or all fields if include is omitted): - TEAMS: Team objects with name, member's owner IDs, and metadata (org-wide, not personal — for the current user's team use get_user_details with include=[TEAMS_AND_ROLES]) - SEATS: Available seat type names in the organization (use these as filters with search_crm_objects on USER objectType to count how many users hold each seat) - JOB_TITLES: Job titles/roles present in the organization - ACCOUNT_INFORMATION: Account timezone, currency, account type, and UI domain </returns> <usage_guidance> - IMPORTANT: Check if user query contains first-person language ("my team", "my role", "my manager", "my direct reports") - If query uses "my", "I", or "me" referring to personal context → Use get_user_details instead - EXCEPTION: "my teams" or "which teams am I on" (plural) should use this tool since get_user_details only returns a single primaryTeam - If query is organization-wide ("our marketing team", "the sales team", "all managers", "my teams") → Use this tool - Use the include parameter to fetch only what you need and reduce response size - Include TEAMS when you need team membership or structure - Include SEATS when you need available seat types - Include JOB_TITLES when you need roles/job titles to filter users by role - Include ACCOUNT_INFORMATION when you need the account's timezone, currency, account type, or UI domain - To find or count users by role or seat, use the returned job titles or seat types as filters with search_crm_objects on USER objectType - SEATS returns only seat type names, not user counts — you MUST follow up with search_crm_objects to get user counts per seat type - When the user references a team's data (e.g., 'our sales team's deals', 'marketing team pipeline'), use this tool first with include=[TEAMS] to resolve team membership to owner IDs, then pass those IDs as filters to search_crm_objects. - To find "my teams" (plural), call this tool with include=[TEAMS] and find teams with the user's ownerId -- [IMPORTANT]: DO NOT use member name for matching, only use ownerId - [IMPORTANT] If the guidance field is present, read it carefully before responding — it may contain a user-facing message (e.g., missing permissions requiring reauthorization) that must be relayed to the user, or an agent-internal hint (e.g., name disambiguation) that should influence how you process the results </usage_guidance> <examples> <example> <user_query>Who works in sales at my company?</user_query> <action>Use this tool with include=[TEAMS] to get teams, then filter for sales-related ones</action> </example> <example> <user_query>Show me deals for MY team?</user_query> <action>Do NOT use this tool, use get_user_details instead</action> </example> <example> <user_query>Search deals for all marketers</user_query> <action>Use this tool with include=[JOB_TITLES] to find marketing-related roles</action> </example> <example> <user_query>How many users have each seat type?</user_query> <action>Use this tool with include=[SEATS] to get seat type names, then use search_crm_objects on USER objectType filtering by each seat type to count users per seat</action> </example> <example> <user_query>Show me our sales team's deal pipeline</user_query> <action>Use this tool with include=[TEAMS] to get the sales team's member owner IDs, then use search_crm_objects to filter deals by those owner IDs.</action> </example> <example> <user_query>Which teams am I on?</user_query> <action>Use this tool with include=[TEAMS] to get all teams, then find teams that contain the member's ownerID (NOT MEMBER'S NAME)</action> </example> </examples>
get_properties
ChatGPTFetches property definitions including data types and enumeration values. <capabilities> - Particularly useful for discovering valid options in enumeration-type properties - To search for actual data, use search_crm_objects </capabilities> <returns> List of property definition objects containing: - name: Property identifier - label: Display label - description: Property description - type: Data type (string, enumeration, number, etc.) - options: For enumeration types, list of valid values with labels </returns> <usage_guidance> - Property details can be unexpectedly large. Consider fetching in batches - It's not advised to pass an objects full list of properties into this tool </usage_guidance>
get_social_channels
ChatGPT<purpose>List the social channels (connected accounts) the user can access in HubSpot and what they can do on each. Networks: FACEBOOK, INSTAGRAM, LINKEDIN, TIKTOK, TWITTER (X), YOUTUBE. Other networks are unsupported (never returned), not disconnected or missing.</purpose> <returns>channels [{channelId, network, handle, name, active, capabilities}]. capabilities: any of READ, DRAFT, SCHEDULE, PUBLISH. active=false: the user must reconnect it in HubSpot before posting.</returns> <usage_guidance>Use it to find a channelId to post to, to check what the user can do on a channel, or to list connected accounts. Narrow it with networks or capability, e.g. capability=PUBLISH for channels the user can post to. To read posts, call read_social_posts or get_social_post_analytics directly: omitting channelIds reads every channel, and networks reads one network's.</usage_guidance> <scope>Requires the approved Social connector app permission.</scope>
get_social_post_analytics
ChatGPT<purpose>Get published social posts with engagement (likes, comments, shares, clicks) and impressions, including posts published directly on the network. Networks: FACEBOOK, INSTAGRAM, LINKEDIN, TIKTOK, TWITTER (X), YOUTUBE.</purpose> <returns>posts [{broadcastGuid, postKey, source, network, channelId, channelName, publishAt, url, hubspotUrl, stats, content}] and hasMore. stats {likes, comments, shares, clicks, impressions}; a count that isn't reported is left out, never 0. content only with include=[CONTENT]. External posts (source=EXTERNAL) have no broadcastGuid; use postKey.</returns> <usage_guidance>Use for published history and performance: top posts (sortBy), engagement of specific posts, posts published outside HubSpot, and, with query, whether a topic was already covered. Filter by network with networks; it needs no get_social_channels call. For drafts and scheduled posts, use read_social_posts. Call tool_guidance for parameters, what the returned fields mean, sorting, paging, and examples.</usage_guidance> <scope>Requires the approved Social connector app permission.</scope>
get_user_details
ChatGPTReturns user, team and hub info; CRM/marketing object and tool availability. <usage_guidance> - This tool must be used before performing any operations with Hubspot tools to determine the identity of the user, and permissions they have on their Hubspot account - This tool only return information for the current user. Search for "users" objectType using the search_crm_objects tool to find other users/owners in the HubSpot account - This tool provides the availability of crm object types to the current user. Use these values in tools which expect crm object type parameters - This tool provides more accurate availability of the other tools provided by this MCP service. This is critical when tool returned in the response is not AVAILABLE - Every non AVAILABLE object type or tool requires some user interaction to resolve, noting that some issues cannot be resolved by just the user themselves - Each object type returns TWO separate availability statuses: read for view/search operations and write for create/update operations. Check the appropriate permission based on the operation you intend to perform - Use the "include" param to request only the sections you need; omitting it or passing an empty list returns USER_INFORMATION and TOOL_INFORMATION only — TEAMS_AND_ROLES must be explicitly requested - For account-level settings (timezone, currency, account type, UI domain), use get_organization_details with include=[ACCOUNT_INFORMATION] instead of this tool - TEAMS_AND_ROLES returns context specific to the current user only (their primary team, job title, direct reports); for org-wide team or role data, including "my TEAMS", use get_organization_details - IMPORTANT: directReports are not the same as team members. If directReports is empty and the user asked about direct reports: stop, inform the user that no direct reports are configured, and ask whether they want to proceed with team members instead — do not automatically substitute team members for direct reports </usage_guidance> <availability_guidance> <status name="AVAILABLE">It is free to use without issue</status> <status name="REQUIRES_REAUTHORIZATION">The user needs to perform a new authorization flow through HubSpot to unlock new access. This is possible through disconnecting and reconnecting the HubSpot connector through their settings</status> <status name="REQUIRES_PERMISSION_MODIFICATION">The user lacks the correct permission in their HubSpot account. If the only way to resolve a task is to use this tool or object, you should inform the user of their lacking permissions and let them decide if they want to ask their administrator for more privilege</status> <status name="REQUIRES_ACCOUNT_MODIFICATION">The whole HubSpot account lacks the correct permissions and would require an account upgrade. Again, inform the user about these tools or objects only if the presented task can only be solved using them</status> <status name="BLOCKED_FOR_PORTALS_WITH_SENSITIVE_DATA">The operation involves sensitive data, and no troubleshooting will unblock usage of the object or tool. If the only way to resolve a task is to use this tool or object, inform the user of the issue and ask them how they would like to proceed</status> <status name="NOT_AVAILABLE">There is no action the user can take to enable the object or tool. It is simply unavailable for use</status> </availability_guidance> <returns> - Always returned: user ID and Hub ID (accountId) - Only fields listed in the include parameter are returned (or all fields if include is omitted): - USER_INFORMATION: owner ID, name, and email for the current user - TOOL_INFORMATION: a mapping of CRM object types to separate read and write availability statuses; a mapping of other MCP tools to current availability - TEAMS_AND_ROLES: the current user's job title, assigned seats, primary team with member owner IDs, and direct report owner IDs (personal context only — use get_organization_details for org-wide team/role data) - If the guidance field is present, STOP and relay its message to the user — it indicates requested sections could not be returned and the user needs to reauthorize the app </returns> <examples> <example> <user_query>Compare workload across my direct reports</user_query> <action>Call with include=[TEAMS_AND_ROLES]. If directReports is empty, ask the user if they would like to compare workload across their primary team members instead. DO NOT use team members unless user confirms.</action> </example> </examples>
manage_aeo_prompts
ChatGPTRead AI responses to tracked prompts, or create and run new tracked prompts. Provide exactly one operation: DETAIL (a single prompt's per-run AI response text, citations, and mentions for an assistant and date window) or CREATE (start tracking new prompts and run them immediately). CREATE requires a confirmed=false preview before confirmed=true. Call get_aeo_metrics with include=[BUSINESS_UNITS] then include=[ICPS_AND_PRODUCTS] to get the businessUnitId, icpIds, and productIds that CREATE needs. Call tool_guidance (mcpToolInstructions) for the confirmation workflow and per-operation details.
manage_aeo_recommendations
ChatGPTList and inspect AI-search brand recommendations for a business unit. Provide exactly one operation: LIST (recommendations for a business unit, filterable by status/prompt), DETAIL (one recommendation enriched with action-status fields), or START_ACTION. Call get_aeo_metrics with include=[BUSINESS_UNITS] first to get the businessUnitId. Starting a recommendation's action isn't available through the assistant yet — START_ACTION returns a message directing the user to complete it in HubSpot AEO. Call tool_guidance (mcpToolInstructions) for per-operation details.
manage_blog_post
ChatGPTCreate, update, publish, and inspect HubSpot blog posts. One action per call. Read actions: GET_POST, GET_AUTHOR, LIST_BLOGS, LIST_BLOG_POSTS, LIST_TAGS, GET_BRAND_KIT. Write actions: CREATE, UPDATE, SET_AUTHOR, PUBLISH, UNPUBLISH. A blog post is rich text (an HTML body) plus metadata and tags, NOT a module grid — there are no module/layout actions. Posts are created as DRAFTS; PUBLISH is a separate explicit action. PUBLISH requires the post to already have a metaDescription and an author, so set both (via UPDATE and SET_AUTHOR) before publishing. Read before you write: call action=GET_POST to capture the current title, body, metadata, and tags before editing. Write actions mutate the same shared draft, so issue them ONE AT A TIME — never concurrently. Creating a post is confirm-first: describe the post to the user (title, outline, which blog) IN CHAT and get their explicit confirmation before calling CREATE. If the user hasn't said which blog to use, call action=LIST_BLOGS and pass the chosen id as blogId. This tool can also list existing posts: call action=LIST_BLOG_POSTS when the user wants to browse posts or edit one without knowing its contentId; optionally pass blogId to scope the list. Tagging: before setting tags on CREATE or UPDATE, call action=LIST_TAGS and reuse existing tags whose names fit, using their exact names; tags are matched by exact name, so a near-variant (e.g. "Content Marketing" when "Marketing" already exists) creates a duplicate instead of reusing it. Do not create new tags on your own — if none of the existing tags fit, ask the user before setting createNewTags=true, and if they don't approve, add no tags. This tool never renders a card. After your LAST edit (or after CREATE or PUBLISH), call render_asset with assetType=BLOG_POST and assetId=contentId to show the finished post. Typography and color: HubSpot blog templates often set font-family and color on individual HTML elements. When changing the body font or text color, put the inline style directly on every affected text-bearing element, such as h2, h3, p, li, a, and span. For example: <h2 style="font-family: Georgia, serif;">…</h2><p style="font-family: Georgia, serif;">…</p>. Do not put font-family or color only on a wrapping <div>: a template rule on a child element can override that inherited value. Examples: action=LIST_BLOGS -> blogsJson with each blog's id and name. action=LIST_BLOG_POSTS blogId=456 limit=10 -> postsJson with existing post summaries. action=CREATE title="…" postBody="<h2>…</h2><p>…</p>" tags="Marketing, SEO" -> contentId + editorUrl. action=GET_POST contentId=789 -> postJson with title, body, metadata, and tags. action=UPDATE contentId=789 postBody="<h2>Intro</h2><p>…</p>" -> verifiedChangesJson. Read actions require 'blog-post-read' or 'blog-posts-write'. GET_POST for a tagged post additionally requires 'blog-tags-read' to return tag names. Write actions require 'blog-posts-write'; non-empty tags additionally require 'blog-tags-read' and 'blog-tags-write'; PUBLISH additionally requires 'blog-posts-publish'.
manage_campaign_objects
ChatGPTCreates or updates HubSpot marketing campaigns and manages asset associations. <prerequisites> Use CRM tools to retrieve the campaign's campaignCrmObjectId before using CAMPAIGN_UPDATE or CAMPAIGN_ASSET operations. </prerequisites> <mandatory_confirmation_process> Always show proposed changes in a table and get explicit user approval before creating or updating campaigns or modifying asset associations. This step is CRITICAL. <confirmation_rules> - First confirmation only: Add this line after the approval prompt: "Want to skip confirmations for this chat? Just ask." - After 1 confirmation: Stop offering the skip option, but keep confirming - If user opts out: Skip confirmations for remainder of session </confirmation_rules> <confirmation_format> Proposed Changes: | operationType | Field | Value | |-----------------|-------------|-------------------| | CAMPAIGN_CREATE | displayName | Q3 Brand Campaign | Approve? [✅ Yes / ❌ No] Want to skip confirmations for this chat? Just ask. </confirmation_format> </mandatory_confirmation_process> <operations> The operationType field is required on every request: - CAMPAIGN_CREATE: set createRequest with required displayName, optional startDate, endDate, goal, audience, notes, customProperties. - CAMPAIGN_UPDATE: set updateRequest with required campaignCrmObjectId, optional displayName, startDate, endDate, goal, audience, notes, customProperties. - CAMPAIGN_ASSET: set assetRequest with required campaignCrmObjectId, assetOperations (non-empty list of {action, assetObjectType, crmObjectIds}). Each entry has its own ADD|REMOVE action. Check assetOperationFailures in the response — if non-empty, those operations failed; succeeded ones are already applied. Call CAMPAIGN_ASSET_TYPES_LIST first. - CAMPAIGN_ASSET_TYPES_LIST: no additional fields required. </operations>
manage_crm_objects
ChatGPTCreates or updates CRM objects with properties. Create object associations. <prerequisites> Use the get_user_details tool to identify the ownerId and check supported object types. </prerequisites> <mandatory_confirmation_process> Always show proposed changes in a table and get explicit user approval before creating or updating CRM objects. This step is CRITICAL for you to use this tool correctly. <confirmation_rules> - First confirmation only: Add this line after the approval prompt: "Want to skip confirmations for this chat? Just ask." - After 1 confirmation: Stop offering the skip option, but keep confirming - If user opts out: Skip confirmations for remainder of session </confirmation_rules> <confirmation_format> Proposed Changes: | Object Type | ID | Property | Current Value | New Value | |-------------|-----|----------|-----------------|--------------------| | Contact | 123 | email | old@example.com | new@example.com | Approve? [✅ Yes / ❌ No] Want to skip confirmations for this chat? Just ask. </confirmation_format> </mandatory_confirmation_process> <creating_associations> To create associations between CRM objects: - Use the createRequest attribute to create a new CRM object and associate it with an existing CRM object - Use the updateRequest attribute to associate two existing objects - ALWAYS ask user to confirm which specific objects should be associated before creating associations - Example workflow: create contact → get contact ID → find company ID → confirm with user → create an association </creating_associations> <guidance> - Limit upsert objects and associations to a MAXIMUM of 10 objects per request - Not all properties are editable. Use search_properties tool to list available properties or search_crm_objects to sample existing data before making changes </guidance>
manage_custom_object_types
ChatGPTWrites custom CRM object types. Each schema in the request has an action field that determines the operation to perform. A single request may mix actions. <confirmation> CRITICAL: Show proposed schemas in a summary table and get explicit user approval before writing, then set confirmationStatus to CONFIRMED. If the user explicitly opts out of confirmations, skip the table and set CONFIRMATION_WAIVED_FOR_SESSION. </confirmation> <result_handling> Write tools return per-item results. Each has a succeeded flag and either successDetails or failureDetails. Always report each result clearly. If failures are remediable, fix & retry them. For each success, share its settingsLink. A succeeded result means the change is saved. The discoverHubspotSchema tool can take up to a minute to reflect it, so don't re-read the schema to verify a succeeded write. </result_handling> <confirmation_format> == Custom Object Types == - Pets: <description> - Primary display property: Name (Text) - Secondary display property: Age (Number) - Associated with: Contacts, Tickets - Vendors - Primary display property: Capacity (Number) [before: Name (Text)] Approve? [Yes / No] </confirmation_format> <custom_object_type_write_rules> - Singular/plural label forms must be under 50 characters, and not match any existing object type labels. - Create custom object types FIRST, before adding properties, pipelines, or association labels to them — the write returns the new objectTypeId needed for subsequent operations. - When associating two new custom objects: create the first, then use its objectTypeId in the second's objectTypeIdsToAssociate. </custom_object_type_write_rules>
manage_custom_pipelines
ChatGPTCreates custom pipeline schemas on CRM object types. Custom pipelines are available to paid tiers (Starter and above). <default_pipeline_editing> If portal does not have access to custom pipelines, can edit the default HubSpot-provided pipeline instead. If the user confirms this is okay, set shouldEditDefaultPipelineInstead to true, and provide one schema. </default_pipeline_editing> <mandatory_confirmation_process> Always show proposed schemas in a summary table and get explicit user approval before creating. This is CRITICAL. Set confirmationStatus to CONFIRMED after the user approves, or CONFIRMATION_WAIVED_FOR_SESSION if the user has opted out of per-action confirmations for the remainder of the session. </mandatory_confirmation_process> <write_result_handling> Write tools return per-item results. Each result has a succeeded flag and either successDetails or failureDetails. Always check each result, reporting successes/failures clearly to the user. If failures are remediable, fix and retry those failures. For successes, share the settingsLink from each successDetails with the user. </write_result_handling> <confirmation_format> == Pipelines == Ticket Support Escalation: <description> - New (OPEN) -> In Progress (OPEN) -> Escalated (CLOSED) -> Resolved (CLOSED) Deal Enterprise Sales: <description> - Prospecting (15%) -> Qualification (40%) -> Success (100% - Closed Won) -> Failure (0% - Closed Lost) Approve? [Yes / No] </confirmation_format> <custom_pipeline_stage_metadata_rules> DEAL (0-3): - probability (REQUIRED): decimal 0.0-1.0 (NOT percentage, NO % sign) - state: null LEAD (0-136): - probability: null - state (REQUIRED): one of 'NEW', 'IN_PROGRESS', 'QUALIFIED', 'UNQUALIFIED' NON-DEAL NON-LEAD: - probability: null - state (REQUIRED): 'OPEN' (active/in-progress) or 'CLOSED' (terminal/completed) - for TICKET (0-5), must be at least one 'OPEN' and one 'CLOSED' stage </custom_pipeline_stage_metadata_rules>
manage_custom_properties
ChatGPTCreates custom property schemas on CRM object types. <mandatory_confirmation_process> Always show proposed schemas in a summary table and get explicit user approval before creating. This is CRITICAL. Set confirmationStatus to CONFIRMED after the user approves, or CONFIRMATION_WAIVED_FOR_SESSION if the user has opted out of per-action confirmations for the remainder of the session. </mandatory_confirmation_process> <write_result_handling> Write tools return per-item results. Each result has a succeeded flag and either successDetails or failureDetails. Always check each result, reporting successes/failures clearly to the user. If failures are remediable, fix and retry those failures. For successes, share the settingsLink from each successDetails with the user. </write_result_handling> <confirmation_format> == Properties == Deal Risk Level (Drop-down): <description> - High - Medium - Low Loss Condition (String): <description> Approve? [Yes / No] </confirmation_format> <custom_property_write_rules> Behavioral Rules: - label & description should be in the user's language (and if english, label uses Sentence case) - You should NEVER recommend any property that could contain sensitive information or PII. - groupName should use pattern '{objectType}_information' (e.g., 'deal_information', 'contact_information') - Never show or mention the fieldType to the user - just reference the overall type. Valid Type/FieldType Pairings: - string → text - bool → booleancheckbox - enumeration → select/checkbox - date → date - datetime → date - number → number - currency_number → number - email → text - url → text </custom_property_write_rules>
manage_landing_page
ChatGPTCreate, edit, style, publish, clone, and inspect HubSpot landing pages. One action per call. Reads: MODULES, MODULE_TYPES, MODULE_DEF, MODULE_STYLES, MODULE_GUIDE, REVISIONS, TEMPLATES, FORMS, BRAND_KIT, LIST_CUSTOM_MODULES. Writes: CREATE_FROM_TEMPLATE, CREATE_CUSTOM_TEMPLATE, UPDATE_CUSTOM_TEMPLATE, CREATE_MODULE, UPDATE_MODULE, SET_MODULE_FIELDS, SET_MODULE_STYLES, SET_SECTION_STYLES, INSERT, REMOVE, REMOVE_SECTION, MOVE, SET_METADATA, PUBLISH, CLONE, RESTORE_REVISION. Read before write: MODULES before any edit; MODULE_TYPES before INSERT; MODULE_DEF before unfamiliar fields; MODULE_STYLES before SET_MODULE_STYLES. Writes mutate one shared draft — never concurrently. CREATE_MODULE authors a reusable custom module TYPE (not on any page — check LIST_CUSTOM_MODULES first, then INSERT the returned modulePath). BATCH IS THE DEFAULT for compound edits: group SET_MODULE_FIELDS/STYLES/SECTION_STYLES/METADATA/REMOVE/MOVE into one action=BATCH call (operationsJson, sequential server-side, returns batchResults). Max 10 operations per batch; at most one REMOVE/REMOVE_SECTION/MOVE per batch. NOT batchable (always separate): INSERT/CREATE_/UPDATE_/CLONE/PUBLISH/RESTORE_REVISION. If BATCH returns "not currently supported", fall back to sequential calls. CREATE_FROM_TEMPLATE requires explicit user confirmation IN CHAT — choosing a template is NOT confirmation. Confirm before PUBLISH/RESTORE_REVISION/UPDATE_CUSTOM_TEMPLATE. Never renders a card — after your LAST edit or PUBLISH, call the render tool. Examples: action=MODULES contentId=123 -> modulesJson. action=CREATE_FROM_TEMPLATE pageName="Spring Promo" templatePath="..." -> {status,contentId,editorUrl}. action=SET_MODULE_FIELDS contentId=456 moduleId="hero_1" fieldOverridesJson={headline:"Hi"} -> verifiedFieldsJson. action=SET_SECTION_STYLES contentId=456 moduleId="hero_1" stylesJson={backgroundColor:{r:255,g:238,b:0,a:1}} -> verifiedStylesJson. Scopes: reads need landingpages-read or -write; writes need landingpages-write; PUBLISH additionally needs landingpages-publish.
manage_marketing_email
ChatGPTManages a marketing email's settings and content. Call tool_guidance for guidance. Settings sub-operations (_type): - "LIST_SUBSCRIPTION_TYPES" — list subscription types; call before CREATE to get a valid subscriptionTypeId - "LIST_FROM_ADDRESSES" — list verified from addresses; call before CREATE to choose a replyToEmail; if address not listed, list options and stop - "CREATE" — create a new email (required: name, subject, fromName, replyToEmail, subscriptionTypeId; permanent fields — ask the user BEFORE calling CREATE: templatePath: ask template or blank? call LIST_TEMPLATES to show options; brandId; emailType: BATCH by default, AUTOMATED for workflow emails) - "POLL_EMAIL_CREATION" — poll for CRM object; takes marketingEmailId - "UPDATE" — update email settings; template/brandId cannot be changed after creation - "CLONE" — clone into a new draft - "GET_EMAIL_DETAILS" — retrieve current settings - "GET_TEMPLATE" — retrieve a template by path - "LIST_TEMPLATES" — search/browse templates by kind (CODED or DND) and filename Content sub-operations (marketingEmailObjectId): - "GET_CONTENT" — returns the editable layout - "EDIT_CONTENT" — always call tool_guidance; resubmit full layout; preserve all styling, only change text/links/images - "PREVIEW_CONTENT" — renders the email; returns subjectLine, renderedText, (optional) renderedHtml - "AB_TEST_EMAIL" — set up an A/B test on a draft email by adding Version B; use this whenever the user asks to test two versions, create a version B, split test, or try two subject lines — they often don't say "A/B" explicitly Only draft emails can be edited. Always show proposed changes and get explicit user confirmation before creating, updating, or editing.
manage_onboarding
ChatGPT<purpose>Check whether the user's HubSpot is connected and working. Use it when they ask if it's connected or working, are testing the connection, have just connected, or ask if their CRM is empty or has any data. Also assesses CRM onboarding status and guides the next step.</purpose><usage_guidance>For those connection checks, call this tool right away, without asking first, whatever get_user_details returned for onboarded. Otherwise, call it when get_user_details returns onboarded: false, after answering the user's question and offering to help them get started; do not call it when onboarded: true. Use action to control behavior: leave empty (the default) to just check status. SET_GOAL — records the user's primary goal; requires goal to be set to one of organizeAndTrackContacts, automateMarketing, generateLeads, manageSalesPipeline, customerSupport, billsAndCollectPayment, buildWebsite, createMarketingContent, or stillExploring — map the user's own words to the closest matching value. Only one goal can be stored; setting a new goal replaces any previous one.</usage_guidance><returns>goalStatus: NOT_STARTED or COMPLETE — whether the user has set an onboarding goal; goal: the user's stored goal (present once set); taskGroup: the goal's remaining onboarding tasks (omitted until a goal is set, or when nothing is left to do) — a group with a name, nested childGroups, and tasks, each with a name, description, and link; completed or skipped tasks are excluded; guidance: instructions for you, the agent — when present, follow it and present the returned tasks as options for the user to choose from; do not collapse them into a single step</returns><response_rendering>Render every returned task, including those nested in child groups, as a markdown link [task name](task link) with its description. List all of them (guidance says how many); do not omit or limit. Always render: See all onboarding tasks in your [start guide](guideLink).</response_rendering>
manage_saved_reports
ChatGPTReads and lists saved HubSpot reports. Set action=LIST to search and browse available reports (returns IDs, names, descriptions, and total count). Set action=FETCH to retrieve a single report's full data including its definition and formatted dataset — identify the report by either reportId or reportName. Use LIST first to discover which reports exist, then FETCH to get the data. After a FETCH, display the report by calling render_asset with its ID rather than re-rendering the dataset yourself as a table.
manage_segment
ChatGPTCreate, edit, delete, or restore a segment, or add/remove its records. Set operation.type to CreateStaticSegmentOperation to create a new hand-picked static segment, CreateDynamicSegmentOperation to create a new dynamic (filter-driven) segment whose membership updates automatically, UpdateSegmentOperation to edit an existing segment's name, description, or filter, AddMembersOperation to add records to an existing static segment, RemoveMembersOperation to remove specific records from one, RemoveAllMembersOperation to empty one entirely (kept), DeleteSegmentOperation to delete one, or RestoreSegmentOperation to restore a deleted one. <mandatory_confirmation> This tool writes to the portal. Before calling it, you MUST show the user a summary of the exact action and get explicit approval: - CreateStaticSegmentOperation: the name, object type, and how many records (if any) will pre-populate it. - CreateDynamicSegmentOperation: the name, object type, and the filter that defines membership. - UpdateSegmentOperation: the target segment (list ID) and which of its name, description, or filter change. - AddMembersOperation / RemoveMembersOperation: the target segment (list ID), object type, and number of records added or removed. - RemoveAllMembersOperation / DeleteSegmentOperation: the target segment (list ID), and whether you are emptying it (members removed, segment kept) or deleting it. - RestoreSegmentOperation: the deleted segment (list ID) and any new name. End with an explicit approval prompt (e.g. "Proceed? [Yes / No]"). Leave confirmationStatus as UNCONFIRMED until the user approves; only after they confirm, call the tool with confirmationStatus set to CONFIRMED. Do NOT set CONFIRMED before the user approves, even if the user asks you to "just do it" or to skip confirmation. On the first confirmation in a chat you may also offer to stop asking for the rest of the session; if the user agrees, set confirmationStatus to CONFIRMATION_WAIVED_FOR_SESSION on subsequent calls. </mandatory_confirmation>
manage_social_posts
ChatGPT<purpose>Create, update, or cancel a HubSpot social post.</purpose> <capabilities> action=CREATE: create a post (mode=DRAFT (default) | SCHEDULE | PUBLISH_NOW) on one channel. Requires channelId and content. action=UPDATE: edit, schedule, or publish a draft or scheduled post in place. Requires broadcastGuid; only provided fields change. mode=SCHEDULE schedules or reschedules it; mode=PUBLISH_NOW publishes it now. action=CANCEL: cancel a scheduled post — moves it back to a draft (unschedules it; nothing is deleted). Requires broadcastGuid. Only SCHEDULED posts can be canceled. </capabilities> <returns>action, outcome (NEEDS_CONFIRMATION | DRAFTED | SCHEDULED | PUBLISHING | UPDATED | UNSCHEDULED), a summary, and post (the affected post) with broadcastGuid, status, and a hubspotUrl deep link. PUBLISHING means a publish-now post is queued to go live shortly, not yet published.</returns> <mandatory_confirmation_process>Never writes on the first call: call with confirmed=false to get outcome=NEEDS_CONFIRMATION and the post exactly as it will be; show the user the summary, the full post.content, and any post.title and post.mediaUrls, and end your turn. Call again with identical arguments and confirmed=true only once the user approves in a reply; their request is never approval.</mandatory_confirmation_process> <usage_guidance>Get channelId from get_social_channels and broadcastGuid from read_social_posts. To schedule, pass mode=SCHEDULE on CREATE or UPDATE. It can't delete a post or set its campaign; send the user to HubSpot. Call tool_guidance for the confirmation protocol, channel capabilities, scheduling and time zones, per-network authoring, rendering, and error recovery.</usage_guidance> <prerequisites>fileIds must name files already in HubSpot File Manager; video or more than one file needs fileIds, since mediaUrl takes a single image. Instagram and TikTok need an image or video to schedule or publish; YouTube needs a video.</prerequisites> <scope>Requires the approved Social connector app permission.</scope>
manage_website_page
ChatGPTCreate, edit, style, publish, clone, and inspect HubSpot website pages, and edit the site's navigation menus. Set exactly one operation; the operation's own shape lists the fields it takes, so there are no conditional field rules to infer. Read before you write: read MODULES to capture verbatim current values AND each module's layout position before any edit, MODULE_TYPES before an insert, MODULE_DEF before writing unfamiliar fields, MODULE_STYLES before restyling one. Write operations mutate the same shared draft, so issue them ONE AT A TIME — never in parallel, or they clobber each other. Reads have no side effects and may be batched. Creating a page is confirm-first: present the page and template in chat and get an explicit user confirmation IN CHAT before CREATE_FROM_TEMPLATE — choosing a template is NOT confirmation. This tool never renders a card; after your LAST edit call render_asset with assetType=WEBSITE_PAGE and the contentId as assetId. Confirm with the user before PUBLISH or RESTORE_REVISION, and before any NAV_* write (those are live and site-wide). Reads require website page read access ('sitepages-access' or 'pages-write'); writes require 'pages-write'; PUBLISH additionally requires 'pages-publish'.
query_crm_data
ChatGPTQueries HubSpot CRM data via SQL with HubSpot-specific extensions. IMPORTANT: You MUST call the Tool Guidance tool before your first query. It contains required guidance and examples. <select> IMPORTANT: Property names must exactly match HubSpot internal names. Always call search_properties to confirm names before querying. The record identifier property is hs_object_id. For financial values, prefer properties ending in _in_home_currency. <unsupported>SELECT DISTINCT, AS aliases, CASE WHEN, IF(), string functions (CONCAT, UPPER, etc.), COALESCE, associations.OBJECT.</unsupported> </select> <from> One object type per query: CONTACT, COMPANY, DEAL, TICKET, etc. Use a user-details tool to discover supported types. <unsupported>JOIN, UNION, subqueries, CTEs.</unsupported> </from> <where> Operators — comparison: =, !=, <, >, <=, >=; text/substring match: column LIKE '%value%'; presence: column IS NULL / column IS NOT NULL. List membership: hs_crm_search.ilsListIds = 'LIST_ID' (cannot combine with aggregates or GROUP BY). Date filters: in an aggregation (GROUP BY or aggregate) use a YYYY-MM-DD date, matched by day; in a plain row SELECT either a date or a full timestamp (e.g. '2025-01-01 14:00:00') works. "My"/"I" queries: filter by hubspot_owner_id (see Tool Guidance for resolution steps). </where> <group-by> DATE_TRUNC(prop, 'INTERVAL') — INTERVAL: DAY | WEEK | MONTH | QUARTER | YEAR. MEDIAN(prop) supported alongside standard aggregates. <unsupported>HAVING.</unsupported> </group-by> <order-by> Sort direction: ORDER BY column ASC for ascending, DESC for descending. </order-by> <cross-object> To retrieve associated object data, use OBJECT.property (e.g., SELECT COMPANY.name FROM CONTACT) — NOT associations.OBJECT. associations.OBJECT is for WHERE existence checks only (IS NULL / IS NOT NULL). Never use it in SELECT or GROUP BY. A query can reference at most 2 different associated object types. </cross-object>
query_segments
ChatGPTRead-only lookups that support the manageSegment write operations. Set operation.type to: - SearchSegmentsQuery: find existing segments by name (optionally scoped to an object type or list type) to get the list ID needed for AddMembersOperation, RemoveMembersOperation, or a future update/delete. With deleted=true it searches only deleted segments, to find the list ID for a RestoreSegmentOperation. - SearchFilterInputsQuery: resolve the ids that filter expressions take as arguments — association type ids for ASSOCIATION(...), event type ids and properties for UNIFIED_EVENTS(...), form guids, workflow/import ids, and marketing email triples. Users do not know these ids; look them up here rather than guessing, because a guessed id creates a segment that silently filters on the wrong thing. Each result includes a ready-to-use filter fragment. - GetSegmentQuery: fetch one segment's definition by list ID — its object type, list type, name, description, saved filter expression, exclusions, and access level. Use it to inspect a segment before editing it, or to answer what it filters on or excludes. This returns the definition, not the members. - GetSegmentMembersQuery: list the CRM records inside a segment by list ID (record ID and display name, plus any requested properties), paginated via cursor. This is the only way to read a segment's members: membership is not a CRM property, so a filter search cannot reproduce it. Works for STATIC and DYNAMIC segments. This tool only reads; it never changes the portal and needs no confirmation.
read_campaign_data
ChatGPTREQUIRED FIRST STEP: before your first call, invoke tool_guidance for "read_campaign_data" and follow it; it contains the required parameter details and examples for each operation. Reads campaign data using one of four operations selected by the operation field. GET_ANALYTICS: engagement metrics (sessions, new contacts, influenced contacts) for one or more campaigns. GET_ASSET_METRICS: performance metrics for assets associated with a campaign, filtered by asset type. GET_CONTACTS: paginated contact IDs attributed to a campaign, filtered by attribution type (NEW_CONTACTS_FIRST_TOUCH, NEW_CONTACTS_LAST_TOUCH, INFLUENCED_CONTACTS). GET_CAMPAIGN_ASSET_TYPES: returns the portal-enabled campaign asset types with human-readable aliases (e.g. AUTOMATION_PLATFORM_FLOW → workflows). No additional request parameters needed.
read_social_posts
ChatGPT<purpose>Read the HubSpot Social calendar: draft, scheduled, published, and failed posts managed in HubSpot. Networks: FACEBOOK, INSTAGRAM, LINKEDIN, TIKTOK, TWITTER (X), YOUTUBE.</purpose> <returns>posts [{broadcastGuid, source, network, channelId, channelName, status, publishAt, createdAt, hubspotUrl, content}] and hasMore. content only with include=[CONTENT]. searchNote when a query search didn't reach the oldest posts.</returns> <usage_guidance>Use for planning: what's scheduled, drafts, gaps, cadence, and to read a post by broadcastGuid before editing it. Find a post by its text with query (e.g. a draft about Black Friday). Pass include=[CONTENT] to read post text, and always before editing it. Filter by network with networks; it needs no get_social_channels call. No engagement and no posts published directly on the network: for published history, top posts, and whether a topic was already covered, use get_social_post_analytics. Call tool_guidance for parameters, what the returned fields mean, paging, date ranges, and examples.</usage_guidance> <scope>Requires the approved Social connector app permission.</scope>
render_asset
ChatGPTRenders a HubSpot asset inline as an MCP UI component. Call this after a manage or read tool completes to show the user a visual preview. Pass the assetType matching the asset you just worked with and its assetId.
render_hubspot_home
ChatGPT<purpose>The user's HubSpot home page: a full-page app showing what needs their attention in HubSpot.</purpose><usage_guidance>Takes no input. The app renders the page, so reply in one short sentence and let the user work in it.</usage_guidance><returns>guidance: what the app is showing.</returns>
search_communications
ChatGPTSearches the content of HubSpot CRM communications to answer what was said or where a topic came up. Covers call transcripts, email bodies, notes, meetings, files, knowledge articles, and inbox conversations. Only some file types, under a size limit, are indexed, so a file missing from results doesn't mean it doesn't exist. Searches the actual content, not structured CRM fields. Pass the words you expect to appear in the content; a few work best. For a theme, search words it would use; results are a sample, not a count. Needs a searchQuery, objectFilters, or both; dates and sourceTypes alone are not enough. When the question names a record, scope to it with objectFilters on the first call. Pass both a searchQuery and objectFilters to attribute results across several records, to get links for emails, notes and meetings, or to time-filter by activity date: with objectFilters alone, afterDate and beforeDate apply to when the record was created. Results default to a concise summary; set resultDetail to FULL_TEXT on a follow-up call when you need the complete transcript or body, passing the result's crmObjectType (KNOWLEDGE_ARTICLE or FILE for knowledge articles and files, which have none) and objectId as objectFilters and no searchQuery to fetch only that result. Call summaries are AI-generated and drop details, so follow up with FULL_TEXT before reporting a detail as missing from a call. activityDate is when the activity happened; createdAt is when the record was logged in HubSpot, so don't date activities by it. With a searchQuery, results are ranked by relevance, not date. To order results without activityDate by when they happened, get hs_timestamp from search_crm_objects rather than guessing from content. Use search_crm_objects for property filters or to list communications in a time window with no topic or record, and search_conversations for direct inbox-thread lookups.
search_conversations
ChatGPTSearch or analyze conversation threads, ticket transcripts, and support case messages from HubSpot inboxes. For conversation content tied to a CONTACT, TICKET, DEAL, or COMPANY, including when summarizing or describing a ticket, use this tool, not search_crm_objects/get_crm_objects, which return only record properties, not the message thread. You may use search_crm_objects first to resolve the CRM record ID, then pass it here as objectType + objectId (e.g. objectType=TICKET) to retrieve the thread. Searching NOTE, EMAIL, or CALL engagement objects does not retrieve inbox conversation transcripts. Internal notes and team comments left on a conversation or case live inside the conversation thread, not in NOTE engagements. Retrieve them here with includeAllDialogue=true. Pick one mode per call, or omit all to get the most recent conversations (newest first), with inbox/channel/status filters still applied. Modes: CRM object (objectType + objectId), time range (startTime/endTime), text search (query, with searchMethod=KEYWORD default or SEMANTIC), or aggregation (aggregationDimensions). Text search with either method may combine with time range; no other cross-mode combinations allowed. Aggregation always counts conversations started in the requested window (hs_started_at). Non-aggregation time-range search counts conversations active in the window (hs_lastmodifieddate) — a conversation started before the window but updated within it will appear in time-range results but not in aggregation counts. <usage_guidance> - [Important] For queries like "my conversations" or "our chats" that imply owner/assignee filtering: use the assignedAgentId request filter to narrow to a specific agent's conversations (pass the HubSpot user id, i.e. the <userId> in actor id "A-<userId>"). Each result also includes assignedAgentId for grouping. For wide owner scans, combine with includeMessages=false to scan cheaply - [Important] Attribute agent/rep names by identity, never from message text (signatures are free text and often wrong). Prefer the resolved names this tool already returns: assignedAgentName for a conversation's assignee and, with messageDetail=FULL, senderName on each agent message. Only when a name is absent, fall back to the id (assignedAgentId, or the <userId> in a sender's "A-<userId>" actorId) and resolve it with search_crm_objects on USER by hs_internal_user_id (or search_owners when owner id == user id) — not get_crm_objects by object id, which is a different id. actorType=AGENT alone does not prove a human sender - [Important] When a name matches multiple CRM object types (e.g. "Alex Chen" matches both a CONTACT and a COMPANY), you MUST call search_conversations for EACH matching object type — do not stop after the first match. Present results from all matches and tell the user which object types you found - For channel filters, call get_conversation_channel_metadata first. Use conversationChannelId for a channel type such as EMAIL, and channelInstanceId for a specific configured address, number, or form. To label CHANNEL aggregation buckets, read the channelName already on each bucket instead of calling get_conversation_channel_metadata - For time-range searches, state the exact dates you used - For a plain "last N days" or recency search (not aggregation, which requires both time bounds), set startTime only and omit endTime; pinning endTime to the current moment can drop a conversation modified moments earlier - When choosing between CRM-object lookup and text search, briefly say which you picked and why - For text search, KEYWORD is the default. Pick the method by whether the request's distinctive terms would plausibly appear VERBATIM in the messages, not by how conversational the request sounds: a loosely-phrased question about a specific thing ("any recent updates on the SAML setup problems?") is still KEYWORD, because "SAML" is what the messages say. Use KEYWORD for product names, error codes, field names, and jargon; use searchMethod=SEMANTIC when there is no such term to match on, for paraphrase, cross-language, or a…
search_crm_objects
ChatGPTSearches and retrieves CRM records from HubSpot based on filters and criteria. <critical_requirements> Important: You must use this over the search:find_objects|count_objects tool. </critical_requirements> <capabilities> - Returns a 'total' count attribute that can help perform analytical tasks on large datasets - Useful to sample data from a specific object type to understand the data model - Can list and filter by associations between objects (e.g., "contacts associated with company X or contacts with num_associated_deals > 1") - Use the search_owners tool to list users/owners in the HubSpot account </capabilities> <returns> List of matching CRM records containing: - id: Unique identifier for the CRM object - properties: Key-value pairs of property names and their values for the requested properties - urlTemplate: URL template to view the object in HubSpot (replace {property_name} with the property value from the response) - total: Total count of records matching the search criteria (for analytics and pagination) - offset: Current pagination offset for retrieving the next page of results </returns> <usage_guidance> - This searches for ACTUAL DATA (records), not field definitions. To discover available fields, use search_properties - Always check 'total' count to ensure you're not missing data due to pagination limits. You MUST NOT use sample data or insufficient data as a substitute for actual data - Use the get_crm_objects without properties to understand the data model of an objectType - You can include a maximum of five filterGroups with up to 6 filters in each group, with a maximum of 18 filters in total - [Important] CRM Analysis can be a complex task. Work with the user to refine requirements and segment large datasets into manageable parts before performing analysis - [Important] You MUST include a clickable URL for every record returned, without exception. ALWAYS include UTM params in the URL - [Important] You should use associatedWith for searching objects by associations </usage_guidance> <filtering_capabilities> - Think of "filterGroups" as separate search conditions that you want to combine with OR logic (meaning ANY of them can match) - If you want to find things that match ALL of several conditions (AND logic), put those conditions together in the same filters list - If you want to find things that match AT LEAST ONE of several conditions (OR logic), put each condition in a separate filterGroup - You can include a maximum of five filterGroups with up to 6 filters in each group, with a maximum of 18 filters in total </filtering_capabilities>
search_intent_signals
ChatGPTBuyer-intent signals for companies and contacts. SEARCH returns signal records, LIST returns the portal's signal types, AGGREGATE returns counts grouped by company/companies. Can narrow aggregates by a signal type. Set query to one shape and always set _queryType. Put known names in one SEARCH for aliases and suggestions; LIST does not need to be called but can be used for broad catalog discovery. An unknown field is dropped, not rejected, so check the response matches the filters you asked for.
search_owners
ChatGPTLists and searches for owners who can be assigned to CRM records. <capabilities> - Supports searching by name/email or batch lookup by owner IDs - HubSpot owner ids and user IDs are distinct, lookups only work when owner ids are provided specifically </capabilities> <returns> List of owner objects containing: - ownerId: The ID to use for hubspot_owner_id assignments - name: Display name of the owner - isActive: Whether the owner is currently active </returns> <examples> <example> <description>Search by name</description> <query>{"searchQuery": "John Smith"}</query> </example> <example> <description>Lookup specific IDs</description> <query>{"ownerIds": [12345, 67890]}</query> </example> <example> <description>Paginate results</description> <query>{"limit": 50, "offset": 50}</query> </example> </examples>
search_properties
ChatGPTFinds the most relevant CRM property definitions using keyword-based search. <critical_requirements> Important: You must use this over the fetch tool to get HubSpot CRM Objects. </critical_requirements> <capabilities> - Lists all property definitions for specified object type when no search terms provided - To search for actual data, use search_crm_objects </capabilities> <returns> A filtered list of properties matching the search criteria containing: - name: Property identifier - label: Display label - description: Property description - matchScore: Relevance score for the property based on the search query (absent if no query is provided) </returns> <usage_guidance> - Use keywords field for multiple related property guesses in a SINGLE request (recommended for performance) - MAXIMUM OF 5 KEYWORDS ALLOWED PER REQUEST - exceeding this limit will return a validation error - Keywords should be property name guesses, not natural language phrases - Use query field for backward compatibility with single property guess - No search terms provided: Returns ALL properties for the object type (useful for discovery) </usage_guidance> <examples> <example> <user_input>total number of open tickets grouped by urgency</user_input> <thoughts>Customer is asking for total number of open tickets grouped by "urgency". I will look for the best matches on the "urgency" property for the "TICKET" object type.</thoughts> <query>{"objectType": "TICKET", "keywords": ["urgency"]}</query> </example> <example> <user_input>calls assigned to me</user_input> <thoughts>Customer is asking us to filter by calls assigned to them. I have a few guesses for what that property might be called: "assigned_to", "assignee", "owned_by", or "owner". Let me search for those on the "CALL" object type in one efficient request.</thoughts> <query>{"objectType": "CALL", "keywords": ["assignee", "assigned_to", "call_owner", "owned_by"]}</query> </example> <example> <user_input>list each company with its name, employees amount, zip code, and when we last touched base</user_input> <thoughts>Customer is asking us to list companies by a few attributes. I will guess keywords for each of those properties and search for them on the "COMPANY" object type in one request.</thoughts> <query>{"objectType": "COMPANY", "keywords": ["name", "employees", "zip_code", "last_contact"]}</query> </example> <example> <user_input>tickets for this year to identify top 10 most problems our customers face</user_input> <thoughts>Customer is asking us to analyze tickets. I will return all properties for the "TICKET" object type to help with discovery.</thoughts> <query>{"objectType": "TICKET"}</query> </example> </examples> <common_mistakes> - Do not exceed 5 keywords per request (will return validation error) - Keywords should be property name guesses, not natural language phrases </common_mistakes>
show_feedback_form
ChatGPTOpens an interactive feedback form for the user to send feedback about the HubSpot connector to HubSpot. <scope> EXCLUSIVELY for feedback about HubSpot connector tools (search_crm_objects, manage_crm_objects, get_properties, etc.). Do NOT use for: - Non-HubSpot tools (Slack, Microsoft 365, Notion, iMessage, Intercom, etc.) - General AI/LLM quality issues (wrong answers, hallucinations, formatting) - HubSpot product/UI issues unrelated to the connector If the issue is with a non-HubSpot tool, do NOT invoke this tool; tell the user this feedback channel is for HubSpot connector issues only. </scope> <routing> If submit_feedback is available in your toolset, call it directly — do NOT call this tool. A successful response here does not mean the form rendered; clients without MCP UI support still return success. </routing> <when_to_invoke> - Agent-detected: user corrects HubSpot connector behavior, reports wrong data/errors, or is dissatisfied with a HubSpot connector tool. - User-initiated: explicit requests ("I want to give feedback"), indirect asks ("HubSpot should know...", "Tell HubSpot..."), or any clear intent to send feedback to HubSpot. </when_to_invoke> <agent_detected_flow> 1. Complete your response FIRST (give the corrected answer). 2. At the END, add a divider (---), then on a NEW LINE acknowledge the trigger ("I noticed you had to correct that"), offer feedback ("Want to share feedback on the connector?"), and make it optional ("Just ask anytime — I'll send it to HubSpot."). 3. If user opts in: call this tool to show the form. 4. If user declines or doesn't respond: continue normally. Never ask again this session. </agent_detected_flow> <user_initiated_flow> 1. Acknowledge: "Happy to help — opening the feedback form now." 2. Call this tool to show the form. </user_initiated_flow> <critical_requirements> - NEVER suggest Claude/ChatGPT thumbs up/down buttons send feedback to HubSpot. Those go to Anthropic/OpenAI only. ONLY this tool sends feedback to HubSpot. </critical_requirements>
submit_feedback
ChatGPTCollects and submits user feedback about the HubSpot connector to HubSpot. Only after the user explicitly confirms the exact feedback to send. <scope> EXCLUSIVELY for feedback about HubSpot connector tools (search_crm_objects, manage_crm_objects, get_properties, etc.). Do NOT use for: - Non-HubSpot tools (Slack, Microsoft 365, Notion, iMessage, Intercom, etc.) - General AI/LLM quality (wrong answers, hallucinations, formatting) - HubSpot product/UI issues unrelated to the connector If the issue is not about a HubSpot connector tool, do NOT initiate feedback - tell the user this channel is for HubSpot connector issues only. </scope> <when_to_invoke> Agent-detected: user corrects HubSpot connector behavior, reports it returned wrong data/errors, or is dissatisfied with a HubSpot connector tool. User-initiated: explicit requests ("I want to give feedback"), or intent to reach HubSpot ("HubSpot should know...", "Tell HubSpot..."). </when_to_invoke> <flow> 1. Agent-detected only: finish your answer first, then after a divider (---) note the connector issue and OFFER feedback; if declined, continue and never ask again this session. 2. Ask the user to describe the issue in their own words; WAIT. 3. Preview "Here's what I'll send to HubSpot: [their exact words]. Should I go ahead?" and WAIT for confirmation. 4. Only call this tool once the user confirms. </flow> <critical_requirements> - NEVER call without explicit user confirmation of the feedback to send. - The feedback field MUST be the user's own words - never auto-generate or paraphrase. - Claude/ChatGPT thumbs up/down send feedback to Anthropic/OpenAI, NOT HubSpot; only this tool sends to HubSpot. - NEVER submit feedback about non-HubSpot tools or connectors. </critical_requirements>
tool_guidance
ChatGPT<purpose> Retrieves guidance and usage instructions for a set of HubSpot tools. </purpose> <when_to_use> - If a tool's description isn't enough to commit to using it - To find if a tool's inputs or outputs have further semantic meaning - To learn understand if and how certain tools can work together </when_to_use>
update_home_page
ChatGPT<purpose>Writes for the HubSpot home app: refreshes the user's home feed, or takes a task the user completed off it.</purpose><usage_guidance>Only the HubSpot home app calls this tool. Don't call it yourself.</usage_guidance>
Get campaign analytics
ClaudeGet campaign asset metrics
ClaudeGet campaign attribution reports
ClaudeGet campaign contacts by type
ClaudeGet conversation channel metadata
ClaudeGet marketing email analytics
ClaudeManage Onboarding
ClaudeManage marketing email
ClaudeSearch conversations
ClaudeTool Guidance
Claudeask_breeze
Claudediscover_hubspot_schema
Claudeget_aeo_metrics
Claudeget_campaign_attribution_reports
Claudeget_content_analytics
Claudeget_content_analytics_report
Claudeget_conversation_channel_metadata
Claudeget_crm_objects
Claudeget_marketing_email_analytics
Claudeget_organization_details
Claudeget_properties
Claudeget_social_channels
Claudeget_social_post_analytics
Claudeget_task
Claudeget_user_details
Claudeimport-claude-design-from-url
Claudemanage_aeo_prompts
Claudemanage_aeo_recommendations
Claudemanage_blog_post
Claudemanage_campaign_objects
Claudemanage_crm_objects
Claudemanage_custom_object_types
Claudemanage_custom_pipelines
Claudemanage_custom_properties
Claudemanage_landing_page
Claudemanage_marketing_email
Claudemanage_onboarding
Claudemanage_saved_reports
Claudemanage_segment
Claudemanage_social_posts
Claudemanage_website_page
Claudequery_crm_data
Claudequery_segments
Clauderead_campaign_data
Clauderead_landing_page_ui
Clauderead_social_posts
Clauderender_asset
Clauderender_hubspot_home
Clauderender_landing_page_ui
Claudesearch_communications
Claudesearch_conversations
Claudesearch_crm_objects
Claudesearch_intent_signals
Claudesearch_owners
Claudesearch_properties
Claudeshow_feedback_form
Claudesubmit_feedback
Claudetool_guidance
Claudeupdate_task
Claude