Skip to main content
Glama

Metadata MCP Connector

Create Bombora Audience

create_bombora_audience

Create Bombora buyer intent audiences on the Metadata platform. Creates B2B audiences based on buyer intent topics, company firmographics, contact attributes, and geographic targeting.

            IMPORTANT PREREQUISITE:
            Before using this tool, call get_intent_topics first to verify that Bombora topics are available.
            If get_intent_topics returns NO topics (empty list), Bombora is NOT available for this account —
            do NOT suggest or use this tool. Instead, recommend creating a firmographic audience
            (create_firmographic_audience) as the preferred alternative.
            Firmographic audiences are the default and most commonly used audience type.

            WHEN TO USE:
            - ONLY after get_intent_topics confirms that Bombora topics are available
            - Create targeted B2B audiences based on buyer intent signals using Bombora data
            - Target companies by industry, size, and employee count
            - Target contacts by seniority level and job function
            - Target specific buyer intent topics (e.g., Pardot, Salesforce)
            - Set geographic targeting and contact limits per company

            BUYER INTENT TOPICS:
            Use the get_intent_topics tool to retrieve available intent topics before creating the audience.
            Intent topics represent buyer interest areas such as:
            - CRM solutions (e.g., Pardot, Salesforce)
            - Marketing automation platforms
            - Analytics and BI tools
            - And many others based on available topics

            TARGETING OPTIONS:
            - Intent Topics: Use topic values from get_intent_topics (required for Bombora audience)
            - Industries: Use industry IDs. Examples:
              1=Defense & Space, 4=Computer Software, 6=Internet, 7=Semiconductors, 8=Telecommunications,
              11=Management Consulting, 12=Biotechnology, 41=Banking, 42=Insurance, 43=Financial Services,
              80=Marketing & Advertising, 96=Information Technology & Services
            - Employees: "FROM_1_TO_10", "FROM_10_TO_50", "FROM_50_TO_200", "FROM_200_TO_500", "FROM_500_TO_1000", "FROM_1000_TO_5000", "FROM_5000_TO_10000", "OVER_10000"
            - Job Function / Seniority / Job Title / Location: the same contact-criteria fields as the Firmographic and G2 tools (below), so the same criteria carry across audience types.

            CONTACTS CRITERIA:

Use the following parameters to filter and target specific contacts within accounts:

GEOGRAPHIC TARGETING:

  • location_country_ids: Array of country IDs (e.g., [29] for Brazil, [229] for United States)

  • location_state_ids: Array of state IDs (e.g., [5] for California, [32] for New York)

JOB TITLES:

  • job_title_includes: Array of free text strings to include (e.g., ["Software Engineer", "Manager"])

  • job_title_excludes: Array of free text strings to exclude (e.g., ["Senior", "Lead"])

JOB FUNCTIONS: Valid job function IDs and their labels:

  • 1: Marketing, 2: Sales, 3: Customer Service, 4: Finance, 5: Human Resources, 6: Public Relations

  • 7: Media, 8: Design, 9: Engineering, 10: Operations, 11: Legal, 12: Education

  • 13: Health, 14: Real Estate, 15: Accounting, 16: Administrative, 17: Business Development

  • 18: Community and Social Services, 19: Consulting, 20: Entrepreneurship, 21: Information Technology

  • 22: Military and Protective Services, 23: Product Management, 24: Program and Project Management

  • 25: Purchasing, 26: Quality Assurance, 27: Research, 28: Trades

  • job_function_include_ids: Array of job function IDs to include (e.g., [9] for Engineering)

  • job_function_exclude_ids: Array of job function IDs to exclude

SENIORITY LEVELS: Valid seniority IDs and their labels:

  • 2: Manager, 3: Director, 4: VP, 5: CXO, 6: Unpaid, 7: Training

  • 8: Senior, 9: Owner, 10: Entry, 11: Partner

  • seniority_include_ids: Array of seniority level IDs to include (e.g., [10, 7] for Entry and Training)

  • seniority_exclude_ids: Array of seniority level IDs to exclude

CONTACT LIMITS:

  • contacts_per_company_limit: Maximum number of contacts to target per company (optional). Example: 20

USAGE NOTES:

  • All ID fields (countries, states, job functions, seniorities) use numeric IDs from the platform

  • Job titles are free text strings, not IDs

  • Use include parameters to specify which criteria to target

  • Use exclude parameters to filter out contacts matching specific criteria

  • Combine multiple criteria for precise targeting (e.g., Senior Engineers in California)

  • Criteria are combined with AND logic, so all conditions must be met

CONTACTS CRITERIA PARAMETERS(Usually after other initial audience parameters to be described next):

  • location_country_ids: Array of country IDs (optional)

  • location_state_ids: Array of state IDs (optional)

  • job_title_includes: Array of job title keywords to include (optional)

  • job_title_excludes: Array of job title keywords to exclude (optional)

  • job_function_include_ids: Array of job function IDs (optional)

  • job_function_exclude_ids: Array of job function IDs (optional)

  • seniority_include_ids: Array of seniority level IDs (optional)

  • seniority_exclude_ids: Array of seniority level IDs (optional)

  • contacts_per_company_limit: Maximum contacts per company (optional)

              Returns audience details with ID, size estimation, and creation status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "topics": "<topics>"
    },
    "name": "create_bombora_audience"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAudience name (required)
topicsYesArray of buyer intent topics (required). Use get_intent_topics to retrieve available topics. Example: ['Pardot', 'Salesforce']
employeesNoEmployee count ranges for company targeting (optional). Valid values: 'FROM_1_TO_10', 'FROM_10_TO_50', 'FROM_50_TO_200', 'FROM_200_TO_500', 'FROM_500_TO_1000', 'FROM_1000_TO_5000', 'FROM_5000_TO_10000', 'OVER_10000'
industriesNoIndustry IDs for company targeting (optional). Valid range: 1-148. Example: [4, 96]
job_title_excludesNoFree text keywords for job titles to exclude (optional). Example: ['Senior', 'Lead']
job_title_includesNoFree text keywords for job titles to include (optional). Example: ['Software Engineer', 'Manager']
location_state_idsNoState IDs for geographic targeting (optional). Valid US State IDs: 1 (Alabama), 2 (Alaska), 3 (Arizona), 4 (Arkansas), 5 (California), 6 (Colorado), 7 (Connecticut), 8 (Delaware), 9 (Florida), 10 (Georgia), 11 (Hawaii), 12 (Idaho), 13 (Illinois), 14 (Indiana), 15 (Iowa), 16 (Kansas), 17 (Kentucky), 18 (Louisiana), 19 (Maine), 20 (Maryland), 21 (Massachusetts), 22 (Michigan), 23 (Minnesota), 24 (Mississippi), 25 (Missouri), 26 (Montana), 27 (Nebraska), 28 (Nevada), 29 (New Hampshire), 30 (New Jersey), 31 (New Mexico), 32 (New York), 33 (North Carolina), 34 (North Dakota), 35 (Ohio), 36 (Oklahoma), 37 (Oregon), 38 (Pennsylvania), 39 (Rhode Island), 40 (South Carolina), 41 (South Dakota), 42 (Tennessee), 43 (Texas), 44 (Utah), 45 (Vermont), 46 (Virginia), 47 (Washington), 48 (West Virginia), 49 (Wisconsin), 50 (Wyoming), 52 (District of Columbia). Example: [5] for California, [32] for New York
location_country_idsNoCountry IDs for geographic targeting (optional). Valid IDs: 1 (Afghanistan), 2 (Albania), 3 (Algeria), 4 (American Samoa), 5 (Andorra), 6 (Angola), 7 (Anguilla), 8 (Antarctica), 9 (Antigua and Barbuda), 10 (Argentina), 11 (Armenia), 12 (Aruba), 13 (Australia), 14 (Austria), 15 (Azerbaijan), 16 (Bahamas), 17 (Bahrain), 18 (Bangladesh), 19 (Barbados), 20 (Belarus), 21 (Belgium), 22 (Belize), 23 (Benin), 24 (Bermuda), 25 (Bhutan), 26 (Bolivia), 27 (Bosnia and Herzegovina), 28 (Botswana), 29 (Brazil), 30 (British Indian Ocean Territory), 31 (British Virgin Islands), 32 (Brunei), 33 (Bulgaria), 34 (Burkina Faso), 35 (Burundi), 36 (Cambodia), 37 (Cameroon), 38 (Canada), 39 (Cape Verde), 40 (Cayman Islands), 41 (Central African Republic), 42 (Chad), 43 (Chile), 44 (China), 45 (Christmas Island), 46 (Cocos Islands), 47 (Colombia), 48 (Comoros), 49 (Cook Islands), 50 (Costa Rica), 51 (Croatia), 53 (Curacao), 54 (Cyprus), 55 (Czech Republic), 56 (Democratic Republic of the Congo), 57 (Denmark), 58 (Djibouti), 59 (Dominica), 60 (Dominican Republic), 61 (East Timor), 62 (Ecuador), 63 (Egypt), 64 (El Salvador), 65 (Equatorial Guinea), 66 (Eritrea), 67 (Estonia), 68 (Ethiopia), 69 (Falkland Islands), 70 (Faroe Islands), 71 (Fiji), 72 (Finland), 73 (France), 74 (French Polynesia), 75 (Gabon), 76 (Gambia), 77 (Georgia), 78 (Germany), 79 (Ghana), 80 (Gibraltar), 81 (Greece), 82 (Greenland), 83 (Grenada), 84 (Guam), 85 (Guatemala), 86 (Guernsey), 87 (Guinea), 88 (Guinea-Bissau), 89 (Guyana), 90 (Haiti), 91 (Honduras), 92 (Hong Kong), 93 (Hungary), 94 (Iceland), 95 (India), 96 (Indonesia), 98 (Iraq), 99 (Ireland), 100 (Isle of Man), 101 (Israel), 102 (Italy), 103 (Ivory Coast), 104 (Jamaica), 105 (Japan), 106 (Jersey), 107 (Jordan), 108 (Kazakhstan), 109 (Kenya), 110 (Kiribati), 111 (Kosovo), 112 (Kuwait), 113 (Kyrgyzstan), 114 (Laos), 115 (Latvia), 116 (Lebanon), 117 (Lesotho), 118 (Liberia), 119 (Libya), 120 (Liechtenstein), 121 (Lithuania), 122 (Luxembourg), 123 (Macau), 124 (Macedonia), 125 (Madagascar), 126 (Malawi), 127 (Malaysia), 128 (Maldives), 129 (Mali), 130 (Malta), 131 (Marshall Islands), 132 (Mauritania), 133 (Mauritius), 134 (Mayotte), 135 (Mexico), 136 (Micronesia), 137 (Moldova), 138 (Monaco), 139 (Mongolia), 140 (Montenegro), 141 (Montserrat), 142 (Morocco), 143 (Mozambique), 144 (Myanmar), 145 (Namibia), 146 (Nauru), 147 (Nepal), 148 (Netherlands), 149 (Netherlands Antilles), 150 (New Caledonia), 151 (New Zealand), 152 (Nicaragua), 153 (Niger), 154 (Nigeria), 155 (Niue), 157 (Northern Mariana Islands), 158 (Norway), 159 (Oman), 160 (Pakistan), 161 (Palau), 162 (Palestine), 163 (Panama), 164 (Papua New Guinea), 165 (Paraguay), 166 (Peru), 167 (Philippines), 168 (Pitcairn), 169 (Poland), 170 (Portugal), 171 (Puerto Rico), 172 (Qatar), 173 (Republic of the Congo), 174 (Reunion), 175 (Romania), 176 (Russia), 177 (Rwanda), 178 (Saint Barthelemy), 179 (Saint Helena), 180 (Saint Kitts and Nevis), 181 (Saint Lucia), 182 (Saint Martin), 183 (Saint Pierre and Miquelon), 184 (Saint Vincent and the Grenadines), 185 (Samoa), 186 (San Marino), 187 (Sao Tome and Principe), 188 (Saudi Arabia), 189 (Senegal), 190 (Serbia), 191 (Seychelles), 192 (Sierra Leone), 193 (Singapore), 194 (Sint Maarten), 195 (Slovakia), 196 (Slovenia), 197 (Solomon Islands), 198 (Somalia), 199 (South Africa), 200 (South Korea), 201 (South Sudan), 202 (Spain), 203 (Sri Lanka), 205 (Suriname), 206 (Svalbard and Jan Mayen), 207 (Swaziland), 208 (Sweden), 209 (Switzerland), 211 (Taiwan), 212 (Tajikistan), 213 (Tanzania), 214 (Thailand), 215 (Togo), 216 (Tokelau), 217 (Tonga), 218 (Trinidad and Tobago), 219 (Tunisia), 220 (Turkey), 221 (Turkmenistan), 222 (Turks and Caicos Islands), 223 (Tuvalu), 224 (U.S. Virgin Islands), 225 (Uganda), 226 (Ukraine), 227 (United Arab Emirates), 228 (United Kingdom), 229 (United States), 230 (Uruguay), 231 (Uzbekistan), 232 (Vanuatu), 233 (Vatican), 234 (Venezuela), 235 (Vietnam), 236 (Wallis and Futuna), 237 (Western Sahara), 238 (Yemen), 239 (Zambia), 240 (Zimbabwe), 241 (Guadeloupe). Example: [29] for Brazil, [229] for United States
seniority_exclude_idsNoSeniority level IDs to exclude (optional). Valid IDs: 2-11 as listed above
seniority_include_idsNoSeniority level IDs to include (optional). Valid IDs: 2 (Manager), 3 (Director), 4 (VP), 5 (CXO), 6 (Unpaid), 7 (Training), 8 (Senior), 9 (Owner), 10 (Entry), 11 (Partner). Example: [10, 7] for Entry and Training
job_function_exclude_idsNoJob function IDs to exclude (optional). Valid IDs: 1-28 as listed above
job_function_include_idsNoJob function IDs to include (optional). Valid IDs: 1 (Marketing), 2 (Sales), 3 (Customer Service), 4 (Finance), 5 (HR), 6 (PR), 7 (Media), 8 (Design), 9 (Engineering), 10 (Operations), 11 (Legal), 12 (Education), 13 (Health), 14 (Real Estate), 15 (Accounting), 16 (Administrative), 17 (Business Development), 18 (Community Services), 19 (Consulting), 20 (Entrepreneurship), 21 (IT), 22 (Military Services), 23 (Product Management), 24 (Program/Project Management), 25 (Purchasing), 26 (QA), 27 (Research), 28 (Trades). Example: [9] for Engineering
contacts_per_company_limitNoMaximum number of contacts to target per company (optional). Example: 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so safety profile is covered. The description adds the account-availability gating behavior (Bombora may not be provisioned) and states what is returned ('audience details with ID, size estimation, and creation status'), which is valuable context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very long and repetitive: the entire CONTACTS CRITERIA block is pasted twice, ID tables duplicate schema descriptions, and a dangling 'parameters to be described next' sentence points at content already given. The prerequisite and when-to-use guidance is front-loaded, but the body is bloated and inconsistently indented.

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

Completeness4/5

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

For a 13-parameter creation tool with no output schema, the description covers prerequisites, fallback behavior, targeting semantics, and return contents. The main omission is what happens on failure or quota/credit constraints, but the core calling information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter with examples and ID enumerations; most of the description's parameter text is duplicated verbatim from the schema. The one genuinely additive insight is that criteria combine with AND logic and that topics are required for a Bombora audience, but that is a small increment over an already complete schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create Bombora buyer intent audiences') plus the data sources used (intent topics, firmographics, contact attributes, geo). It also implicitly distinguishes itself from the many sibling audience creators (create_firmographic_audience, create_g2_intent_*, create_technographic_audience) by naming Bombora intent explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit prerequisite chain: call get_intent_topics first, and if it returns an empty list, do NOT use this tool and instead recommend create_firmographic_audience. The WHEN TO USE block names concrete use cases and the intended alternative, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources