Demandbase MCP Tool Details
See the following details for each Demandbase MCP tool:
Retrieve Demandbase Reference Data
Use Retrieve Demandbase Reference Data to find values configured in your Demandbase tenant that you want to use as filters in another tool.
Parameters for Retrieve Demandbase Reference Data
Use the following parameters when retrieving tenant-configured reference data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| originalRequest | string | Yes | User query. |
| referenceTypes | array<string> | Yes | Allowed: accountList, keywordSets, keywords, buyingGroup, Persona, buyerRole, activityTypes. accountList, keywordSets, keywords, and activityTypes must each be requested alone; buyingGroup, Persona, and buyerRole may be requested together. |
| accountListFilters | object | No | Only valid when referenceTypes is ["accountList"]. Keys: name (partial match), ownedBy (exact email), isPublic, numberOfAccounts (range), createdAt/updatedAt (ISO-8601 date range). |
| keywordFilters | object | No | Only valid when referenceTypes includes keywordSets/keywords. Keys: keywordSetName (partial match), keywordName (partial match, keywords only), isCompetitor. |
| queryOptions | object | No | Only valid when referenceTypes includes accountList, keywordSets, or keywords. limit (default 5, maximum 100), nextPageToken, order (allowed fields: name, numberOfAccounts, uniqueUsersThisWeek, createdAt, updatedAt, keyword). |
Search Internal Account Database
Use Search Internal Account Database to research companies from your internal Demandbase database.
Important: Search Internal Account Database does not support Advertising campaign data.
See Fields supported by MCP - Your Account Data for a list of parameters.
Search Internal People Database
Use Search Internal Person Database to research known people from your internal Demandbase database.
Important: Search Internal People Database does not support person lists.
See Fields supported by MCP - Your Contact & Lead Data for a list of parameters.
Search External Global Company Database
Use Search External Global Company Database to research companies using Demandbase global B2B intelligence.
Important: Family Tree and Competitors can be returned but not used as filters.
See Fields supported by MCP - Company Data for a list of parameters.
Search External Global People Database
Use Search External Global People Database to research people using Demandbase global B2B intelligence.
Important: To find people at companies returned by External Global Company Database, pass the returned company IDs to companyIdsToInclude. The people search is then limited to those companies.
See Fields supported by MCP - Contact Data for a list of parameters.
Find Net-New Contacts
Use Find Net-New Contacts to find contacts that are not already in your internal Demandbase database.
Important:
- A contact can match multiple Personas, Buyer Roles, or Buying Groups.
- Contacts are returned in smaller sets to manage the number of results, so one response may not include all available contacts.
Prerequisites to Find Net-New Contacts with Demandbase MCP
- Identify the account by Account ID, account name, or account domain.
- Buyer Role and Persona filters depend on Buying Groups configured in Demandbase.
Parameters for Find Net-New Contacts
Use the following parameters to define a Net-New contact search.
| Parameter | Notes |
|---|---|
| netNew | Set to true. |
| companyName | Interpreted as the internal account name when netNew is true. |
| netNewAccountId | Use as an alternative to companyName. |
| buyerRoles | Optional. Valid only when netNew is true. |
| Personas | Optional. Valid only when netNew is true. |
| queryOptions.perPage | 1–50 records per page; default 5. |
Account-Level Intent
Use Account-Level Intent to search for accounts using keyword sets, individual keywords, competitive keyword sets, and trending Intent configured in your Demandbase tenant.
Important:
- Intent data is only available for account records.
- An account can match to multiple Intent signals, so some results may include more than one value.
Prerequisites to Use Account-Level Intent with Demandbase MCP
Configure Intent keyword sets in Demandbase.
Filter for Account-Level Intent
Use the following filters to define account-level Intent results.
| Filter | Description |
|---|---|
| Intent type | Keyword set, individual keyword, or trending Intent |
| Keyword set | One or more tenant-configured keyword set names |
| Keyword | One or more individual Intent keywords |
| Intent strength | High, Medium, or Low |
| Intent date | Accounts with Intent activity on or after a specified date |
Rank Keyword Sets
Use Rank Keyword Sets to identify which of your existing Intent keyword sets best match a campaign, product, or landing page and determine whether to reuse an existing set or create a new one.
Important:
- Rank Keyword Sets is read-only. It does not create or modify keyword sets.
- For tenants with many keyword sets, the tool ranks the 50 most similar sets. The results summary indicates when the evaluation is limited to these sets.
- If no existing keyword set is a strong match, the summary recommends creating a new keyword set.
- Results may take up to one minute for tenants with many keyword sets.
- Results are cached for five minutes. When retrieving additional pages, use the same input parameters and the returned next_page_token to maintain consistent results.
Prerequisites to Rank Keyword Sets with Demandbase MCP
- Configure Intent keyword sets in Demandbase.
- Provide a landing page URL or at least three keywords. A description alone is not sufficient.
Parameters for Rank Keyword Sets
| Parameter | Type | Required | Notes |
|---|---|---|---|
description | string | No | Description of the campaign, product, or topic. Provides additional context but cannot be used alone. |
keywords | array<string> | Conditional | Two- or three-word phrases describing the campaign. Provide at least three keywords if page_url is not specified. |
page_url | string | Conditional | Product or landing page URL. Keywords are extracted from the page and used as context. Required if fewer than three keywords are provided. |
buying_stage | string | No | Buying stage to consider when ranking keyword sets. Allowed values areawareness, consideration, decision. |
limit | integer | No | Maximum number of keyword sets to return. Default is 10. Maximum is 50. Values above 50 are automatically limited to 50. |
page_token | string | No | Token returned from a previous request to retrieve the next page of results. |
Results for Rank Keyword Sets
| Field | Description |
|---|---|
keyword_set_id | Unique identifier of the keyword set. |
keyword_set_name | Name of the keyword set. |
match_strength | Indicates whether the keyword set is a strong or weak match. |
reason | Explanation of why the keyword set does or does not fit the campaign. |
summary | Number of strong and weak matches, recommendation to reuse an existing keyword set or create a new one, and whether the evaluation was limited to the 50 most similar sets. |
next_page_token | Token used to retrieve additional results, when available. |
Evaluate Keyword Set
Use Evaluate Keyword Set to measure how well each keyword in an existing Intent keyword set aligns with your opportunity pipeline. The tool uses your CRM opportunity data to identify how many companies researched each keyword and subsequently opened or won an opportunity.
Important:
- Evaluate Keyword Set analyzes one existing keyword set at a time.
- Evaluate Keyword Set evaluates up to 2,000 keywords per set. The results summary identifies any keywords excluded from the evaluation.
- Evaluate Keyword Set is read-only and does not modify keyword sets or CRM opportunity data.
Prerequisites to Evaluate Keyword Set with Demandbase MCP
- Configure Intent keyword sets in Demandbase.
- Have CRM opportunity data available in your Demandbase tenant.
- Identify the keyword set by its ID or name. You can use Retrieve Demandbase Reference Data to look up keyword set IDs.
Parameters for Evaluate Keyword Set
| Parameter | Type | Required | Notes |
|---|---|---|---|
id | integer | Conditional | ID of the keyword set to evaluate. Provide either id or keywordSetName. |
keywordSetName | string | Conditional | Exact name of the keyword set to evaluate (not case-sensitive). If multiple keyword sets have the same name, use id. |
intent_research_period_days | integer | No | Number of days to look back for keyword research activity. Default is 395. |
opportunity_period_days | integer | No | Number of days to look back for CRM opportunities. Default is 395. |
lead_time_days | integer | No | Lead time used to evaluate keyword research before an opportunity. Default is 90 days. |
page_size | integer | No | Number of keyword results to return per page. Default is 200. Maximum is 1,000. Values above 1,000 are automatically limited to 1,000. |
page_token | string | No | Token returned from a previous request to retrieve the next page of results. |
Results for Evaluate Keyword Set
| Field | Description |
|---|---|
keyword | Keyword evaluated from the selected keyword set. |
researching_companies | Number of companies that researched the keyword during the selected date range. |
companies_before_new_deal | Number of companies that researched the keyword before opening a new opportunity. |
companies_before_deal_won | Number of companies that researched the keyword before winning an opportunity. |
pipeline_match_percent | Percentage of opportunities in the selected period matched to the keyword. Empty when there are no opportunities in the period. |
summary | Groups keywords by their alignment with opportunities: Strong (5% or more), Moderate (1% to less than 5%), Weak (0.1% to less than 1%), Niche (less than 0.1%), Intent activity only, or No Intent signal. Also identifies keywords excluded from the evaluation. |
next_page_token | Token used to retrieve additional results, when available. |
Buying Group Insights
Use Buying Group Insights to assess Buying Group coverage, identify missing Personas or Buyer Roles, and find known people by Buying Group membership.
Important:
- A gap in Buying Groups means the configured Buying Group is missing expected coverage, but a relevant person may exist at the company.
- An account can match to multiple Buying Groups and coverage gaps, so some results may include more than one value.
Prerequisites for Using Buying Group Insights with Demandbase MCP
Configure Buying Groups in Demandbase.
Filters for Account-Level Buying Group Insights
Use the following filters to assess Buying Group coverage at the account level.
| Filter | Description |
|---|---|
| Buying Group name | An exact tenant-configured Buying Group |
| Completeness score | Buying Group completeness from 0–100 |
| Missing persona | Accounts missing a configured persona |
| Missing buyer role | Accounts missing a configured buyer role |
Filters for Person-Level Buying Group Insights
Use the following filters to find known people based on Buying Group membership.
| Filter | Description |
|---|---|
| Buying Group name | Buying Group |
| Buyer Role | Buying Role of the person |
| Buying Group Persona | Persona of the person |
| Member Status | Confirmed or Suggested |
Create Account Brief
Use Create Account Brief to create an account summary using your internal and global Demandbase data.
Important:
- Create Account Brief returns one consolidated brief and uses one account identifier per request.
- Sections may be omitted when source data is unavailable.
Prerequisites to Create Account Brief with Demandbase MCP
- Identify the account by Account ID, account name, or account domain.
- Provide only one identifier at a time.
Parameters for Account Brief
Use the following parameters to define the account for an Account Brief.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| originalRequest | string | Yes | User query. |
| accountId | string | No | Internal account ID. Mutually exclusive with accountName and domain — pass the ID alone when it's already known from a prior lookup. |
| accountName | string | No | Account name to search. |
| domain | string | No | Account domain to search. |
Information Included in Account Brief
Depending on the data available for the account, an Account Brief may include:
| Section | Description |
|---|---|
| Account summary | Name, domain, industry, size, description, owner, status. |
| Sales and pipeline | Journey stage, qualification/pipeline signals, open opportunities, recent sales activity. |
| Engagement and Intent | Recent engagement, web activity, keyword or trending Intent. |
| Buying Group coverage | Buying Groups, completeness, missing Personas, missing Buyer Roles. |
| Company context | Company profile and recent news. |
| Recommended next actions | Evidence-based follow-up suggestions, stakeholder gaps, and Intent themes. |
Submit Feedback
Submit structured feedback about Demandbase MCP tool results or the Demandbase platform. Feedback categories include data quality, feature requests, access or entitlement issues, credits, and latency.
Parameters for Submit Feedback
| Parameter | Type | Required | Notes |
|---|---|---|---|
originalRequest | string | Yes | The user request related to the feedback. |
category | string | Yes | DATA_QUALITY, FEATURE_REQUEST, ACCESS_ENTITLEMENT_ISSUE, CREDITS, OTHERS, or LATENCY_ISSUE. |
feedback | string | Yes | Feedback describing the issue or suggestion. |
toolNames | array | No | Related MCP tool names; maximum 50. |
relatedPrompts | array | No | Related prompts; maximum 50. |
feedbackIds | array | No | Feedback IDs from related tool responses; maximum 50. |
Response
A successful submission returns a feedbackId and confirmation message:
Invalid categories, empty feedback, or optional lists containing more than 50 items return an error field.
Updated about 1 month ago