← Back to all apps

ZoomInfo

Sales And Marketingby ZoomInfo Technologies LLC
Launched Sep 1, 2026 on ChatGPT

Bring ZoomInfo's verified B2B company and professional intelligence into every conversation. Search 100M+ companies and 500M+ professionals with natural language, track job changes and employment history, build targeted prospect and account lists, and enrich contacts and companies with 300+ data points, including verified work emails, direct dials, firmographics, technographics, and org structure.

Go beyond static data. Surface buying intent signals, funding events, hiring trends, and executive-change scoops to know which accounts are in market right now. Run deep account and contact research that combines ZoomInfo's market data with your own CRM and conversation history, built for meeting prep, deal reviews, stakeholder mapping, and relationship intelligence. Find lookalikes of your best customers, get ML-ranked contact recommendations tuned to prospecting, deal acceleration, or renewal motions, and save any result set as an audience in ZoomInfo for activation.

From first touch to renewal, ZoomInfo grounds your AI workflows in the GTM intelligence layer revenue teams already trust. Know who to target, when to reach out, and why.

20ChatGPT Tools
21Claude Tools
ZoomInfo Technologies LLCDeveloper
Sales And MarketingCategory

Use Cases

sales-and-marketingdata-analyticsproductivitydeveloper-toolscommunication

Available Tools

Account Research

account_research
Full Description

Research a company/account/organization using ZoomInfo market data with your CRM and conversation history. Handles both targeted queries ("What's their recent news?") and broad orientation ("What's going on with this account?").

USE THIS WHEN: You need information about a company, organization, or account (their business, news, financials, tech stack, leadership team, recent developments).

DO NOT USE FOR: Individual person research (use Contact Research instead).

ANSWERS QUESTIONS LIKE: • Company context: What does this company do? Who are their competitors? What's their tech stack? • Leadership: Who's in the C-suite? What's the background of their CTO? • Financials: What's their revenue? Have they raised funding recently? • Recent developments: Any recent news or executive changes? • Relationship status: What's our deal status? Who's on the buying committee? • Engagement overview: How engaged are we? Who are our key contacts? • Qualification: What's our MEDDIC status with this account?

DOES NOT HANDLE: • Specific conversation queries ("What exactly did they say about X?") → Use Conversation Intelligence • Detailed engagement timelines or transcripts → Use Engagements • Structured data for export (revenue fields, headcount) → Use Enrich Companies • Raw/paginated signal export (Intent, News, Scoop) for downstream systems or bulk records → Use Enrich Company Signals

FOR BEST RESULTS: Construct queries that frame the user's goal and describe what ideal context would look like. The more the query conveys about the situation and desired outcome, the better the response.

General orientation: "User wants to understand what's going on with this account. Provide broad situational awareness — who they are, how the relationship stands, what's been happening, and anything notable I should know."

Call prep: "User has a meeting tomorrow with their VP of Engineering. Provide context that helps them walk in prepared — understanding of the company, the person, the relationship history, and any active deals or recent developments."

Deal review: "User is presenting this account at forecast. Provide context that supports a confident deal narrative — where the deal stands, who's involved, momentum indicators, and any risks."

Competitive situation: "User is positioning against Salesforce at this account. Provide context that informs competitive strategy — what they use today, how they evaluate, and what we know about their buying process."

Account planning: "User is building a strategic plan for this account. Provide context that supports territory strategy — the opportunity landscape, key relationships, coverage gaps, and growth signals."

RETURNS: Market intelligence: company overview, leadership profiles, products/services, financials, competitors, technology stack, recent news.

Insight signals: recent trigger events — funding, M&A, earnings, layoffs, partnerships, IPO/divestiture, product launches, leadership and buying-committee changes, hiring anomalies, website visits, and intent spikes (directional indicators).

Relationship intelligence: CRM records, buying committee, key contacts, engagement summary, MEDDIC qualification.

REQUIRES: zi_company_id (7-8 digit integer, e.g. '344589814'). Use Search Companies if you have a company name without the zoominfo company id.

CREDITS: Each query consumes ZoomInfo AI credits. Credit consumption scales with the amount of context retrieved and the complexity of inference performed.

Parameters (2 required)
Required
querystring

Natural language query describing the user's goal and what ideal context looks like. Frame the problem and desired outcome — the tool determines what to retrieve. Include the user's situation, immediate need, and anticipated next steps when known. Examples: • "User wants to understand what's going on with this account. Provide broad situational awareness — who they are, how the relationship stands, what's been happening, and anything notable I should know." • "User has a meeting tomorrow with their VP of Engineering. Provide context that helps them walk in prepared — understanding of the company, the person, the relationship history, and any active deals or recent developments."

zoominfoCompanyIdinteger

ZoomInfo company ID to research. Required. Format: Integer (e.g. 344589814). This is not a Salesforce or CRM ID. Use Search Companies to obtain if you have a company name or domain.

Browse Audiences

browse_audiences
Full Description

Browse GTM Studio audiences with basic metadata. Returns a paginated list of audiences. Filter results using createdByName (creator name), type (CONTACT or COMPANY record shape), or searchText (case-insensitive contains match on audience name).

Working with identifiers: This tool returns audience IDs. Use each result's id as audienceId for getAudience, audienceAnalysis, and audience write tools.

Parameters (0 required, 6 optional)
Optional
createdByNamestring

Filter audiences by the name of the user who created them. May be a first name, last name, or full name. Optional.

pageNumberinteger

Page number for the results.

pageSizeinteger

Number of records to return per page. Default is 10; maximum is 25.

searchTextstring

Search audiences by name using a case-insensitive contains match.

typestring

Filter by audience record shape. Use CONTACT for person-level rows and COMPANY for account-level rows. Omit to return both.

Options:CONTACTCOMPANY
userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Browse Engagements

browse_engagements
Full Description

Use this tool to retrieve engagements (meetings and emails). Useful for tracking engagement history with external contacts. Supports filtering by date, zoominfoCompanyId and/or zoominfoContactId. The date range can be set with engagementDateStart and engagementDateEnd (defaulting to the last 7 days). The window between engagementDateStart and engagementDateEnd must be no more than 90 days, with engagementDateStart before engagementDateEnd.

This tool can only return results if the user's organization has set up integrations between ZoomInfo and at least one of its calendar, email, or meeting providers. Reach out to your account manager for more information.

By default, results are returned in chronological order. To get the last few of an item, reverse the sort order with "-chronological".

Does not consume data credits.

Parameters (0 required, 8 optional)
Optional
engagementDateEndstring

End date for filtering engagements (ISO 8601 format, e.g., '2026-06-01T00:00:00Z'). Dates can be any date in the past, or up to 60 days in the future. The default end date is 7 days in the future. The window between Start Date and End Date must be no more than 90 days, with Start Date before End Date. If end date is specified without a start date, the start date will default to 90 days before the end date.

engagementDateStartstring

Start date for filtering engagements (ISO 8601 format, e.g., '2026-06-01T00:00:00Z'). Dates can be any date in the past, or up to 60 days in the future. The default start date is 7 days ago. The window between Start Date and End Date must be no more than 90 days, with Start Date before End Date. If start date is specified without an end date, the end date will default to 7 days in the future, or 90 days after the start date, whichever is sooner.

engagementLimitinteger

Number of engagements to return (default 10, max 50)

engagementTypestring

Filter by type of engagement. Default is `EMAILS_AND_MEETINGS`.

Options:EMAILSMEETINGSEMAILS_AND_MEETINGS
sortstring

Valid values: `chronological` (oldest first) and `-chronological` (newest first). Default: `chronological`.

Options:chronological-chronological
userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zoominfoCompanyIdinteger

Filter engagements by the account's ZoomInfo Company ID. The zoominfoCompanyId is an integer, usually 7 or 8 digits long. It is NOT a salesforce or CRM ID. e.g. '12345678' or '-43211234', but not '0011U00000adQbXQAU'.

zoominfoContactIdinteger

Filter engagements by the participant's ZoomInfo Contact ID. The zoominfoContactId is an integer, usually 7 or 8 digits long. It is NOT a salesforce or CRM ID. e.g. '12345678' or '-43211234', but not '0011U00000adQbXQAU'.

Contact Research

contact_research
Full Description

Research a specific person/contact using ZoomInfo market data with your CRM and conversation history. Handles both targeted queries ("What's their background?") and broad orientation ("Who is this person?").

USE THIS WHEN: You need information about an individual person (their role, background, contact details, career history).

DO NOT USE FOR: Company/organization research (use Account Research instead).

ANSWERS QUESTIONS LIKE: • Professional background: What's their career history? Where did they work before? • Current role: What do they do? What are their responsibilities? • Education & expertise: Where did they go to school? What's their expertise? • Company context: What company do they work for? What does that company do? • Contact info: What's their email? Phone number? LinkedIn? • Recent activities: Any recent news mentions or job changes? • Relationship status: How engaged are they? Are they in our CRM? • Buying involvement: Are they on a buying committee? What's their role in deals?

DOES NOT HANDLE: • Specific conversation queries ("What exactly did they say about X?") → Use Conversation Intelligence • Detailed engagement timelines or transcripts → Use Engagements • Structured data for export (title, email, phone) → Use Enrich Contacts

FOR BEST RESULTS: Construct queries that frame the user's goal and describe what ideal context would look like. The more the query conveys about the situation and desired outcome, the better the response.

General orientation: "User wants to understand who this contact is. Provide broad situational awareness — their background, current role, company, and anything notable I should know."

Meeting prep: "User has a meeting tomorrow with this person. Provide context that helps them walk in prepared — understanding of their role, background, recent activities, and our relationship history."

Outreach planning: "User is planning to reach out to this contact. Provide context that informs a personalized approach — who they are, what they care about, how they engage, and any warm introduction paths."

Champion building: "User wants to build this person into a champion. Provide context that supports relationship development — their influence, interests, engagement patterns, and what motivates them."

Stakeholder mapping: "User is mapping stakeholders for a deal. Provide context that clarifies this person's role — their influence, relationships, decision authority, and how they fit into the buying process."

RETURNS: Contact intelligence: professional background, current role, education, contact information, company context, recent activities.

Relationship intelligence: CRM records, engagement history, buying involvement, communication patterns.

REQUIRES: zoominfoContactId (7-9 digit integer, e.g. '123456789'). Use Search Contacts if you have a contact name or email without the zoominfo contact id.

CREDITS: Each query consumes ZoomInfo AI credits. Credit consumption scales with the amount of context retrieved and the complexity of inference performed.

Parameters (2 required)
Required
querystring

Natural language query describing the user's goal and what ideal context looks like. Frame the problem and desired outcome — the tool determines what to retrieve. Include the user's situation, immediate need, and anticipated next steps when known. Examples: • "User wants to understand who this contact is and their role. Provide broad situational awareness — their background, current position, responsibilities, and anything notable I should know." • "User has a meeting tomorrow with this person. Provide context that helps them walk in prepared — understanding of their role, professional background, recent activities, and our relationship history."

zoominfoContactIdinteger

ZoomInfo contact ID to research. Required. Format: 7-11 digit integer (e.g. '123456789'). This is not a Salesforce or CRM ID. Use Search Contacts to obtain if you have a contact name or email.

Conversation Intelligence

conversation_intelligence
Full Description

Answers natural-language questions about calls, meetings, and emails, scoped to a single engagement, an account, or a contact. Queries should carry the user's detailed intent and relevant conversation context, including any specified date range of interest (default lookback: 365 days). Requires a meeting or email provider configured in ZoomInfo.

USE THIS WHEN:

  • You need to analyze conversations for objections, commitments,

sentiment, next steps, or action items.

  • You need to surface what was actually said in calls, meetings, or

emails — requirements, promises, or concerns.

  • NOT for CRM fields, firmographics, or market data.

ANSWERS QUESTIONS LIKE:

Engagement: "What were the customer's main objections on this call?" · "What was agreed that a follow-up should reference?" Account: "What concerns has this account raised recently? What did we promise them?" Contact: "What has this person told us they care about?"

SCOPING — pass exactly one ID (else BAD_REQUEST):

engagementId — one call, meeting, or email thread in depth. Opaque string from Browse Engagements or this tool's citations; pass verbatim — some email IDs contain literal angle brackets, which are part of the ID; others are opaque tokens. zoominfoCompanyId — synthesize across an account's recent engagements. zoominfoContactId — synthesize across a contact's recent engagements.

SAMPLING (IMPORTANT): Account and contact scopes quote from only the 5 most recent meetings and 5 most recent emails (meetings without stored transcripts are excluded). Account scope additionally draws on account-level intelligence synthesized across full history. For deeper coverage, drill into cited engagementIds.

ENTRY POINT:

Temporal or positional selector ("my most recent call") → enumerate with Browse Engagements (free, deterministic ordering), then pass the engagementId here. Thematic selector ("what concerns have they raised") → start account- or contact-scoped, then ask targeted follow-ups against a cited engagementId. Set includeContent: true (engagementId scope only, default false) only when verbatim text is required — it appends the raw transcript or email body, prefixed "Raw Engagement:"; long transcripts may be truncated; consumes significant context. IMPORTANT: Transcript/email body inclusion is controlled SOLELY by this boolean — never put transcript requests in the query field. If the user asks for a transcript, set this to true and keep the query focused on analytical intent (e.g. summary, key points).

RETURNS: Synthesized answer with inline citations to source engagements, opening with a data-check line and ending with a Coverage section (window searched, N of M engagements reviewed, truncation notes) — read Coverage before treating an answer as exhaustive.

DOES NOT HANDLE:

Exhaustive topic search ("every call mentioning X") — sampling makes topic recall incomplete. Building a full engagement timeline or finding engagement IDs → Browse Engagements. Broad account orientation or company/market research → Account Research. Person background or profile research → Contact Research. Structured firmographic or demographic data for export → Enrich Companies / Enrich Contacts.

QUALITY: Transcription, diarization, and inference are automated; attribution errors and omissions are possible — verify critical facts by calling this tool again with the cited engagementId and includeContent=true to retrieve the full transcript.

CREDITS: Minimum 9 ZoomInfo AI credits per call, scaling with context retrieved and inference complexity.

Parameters (1 required, 4 optional)
Required
querystring

Natural-language question. Include the user's intent, relevant conversation context, and any time period of interest. IMPORTANT: Do NOT include requests for raw transcripts, verbatim text, or full meeting content in the query. Transcript/email body content is controlled exclusively by the includeContent boolean parameter — it is never returned based on the query text. If the user asks for a transcript, set includeContent: true instead of putting "transcript" in the query. Examples: • "What were the customer's main objections on this call?" • "Summarize where things stand with this account based on recent meetings." • "What did this person commit to in our last few conversations?"

Optional
engagementIdstring

Engagement ID — pass verbatim; some email IDs contain literal angle brackets, which are part of the ID; others are opaque tokens. Provide exactly one of engagementId, zoominfoCompanyId, or zoominfoContactId. Examples of possible values: • "<ABCdefGHIjklMNOpqrSTUvwxYZ1234567890abcd_efgh@mail.example.com>" (email) • "aa11bbcc22ddee33ff44gg55hh66ii77jj88kk99ll00mm11nn22" • "xx99yy88zz77aa66bb55cc44" • "mm11nn22oo33pp44qq55rr66ss77tt88_20250101T120000Z"

includeContentboolean

Append raw transcript or email body. engagementId scope only. Default false. This is the ONLY mechanism that controls whether transcript/email body content is included in the response — the query text has no effect on transcript inclusion. Set to true when the user explicitly asks for verbatim text, a full transcript, or the raw email body. Transcripts can be very large — only request when you need verbatim text, and be mindful of context-window limits.

zoominfoCompanyIdinteger

ZoomInfo company ID (integer). Not a CRM/Salesforce ID. Provide exactly one of engagementId, zoominfoCompanyId, or zoominfoContactId. Format: Integer (e.g. 344589814). Use Search Companies to obtain if you have a company name or domain.

zoominfoContactIdinteger

ZoomInfo contact ID (integer). Not a CRM/Salesforce ID. Provide exactly one of engagementId, zoominfoCompanyId, or zoominfoContactId. Format: 7-11 digit integer (e.g. 123456789). Use Search Contacts to obtain if you have a contact name or email.

Enrich Companies

enrich_companies
Full Description

Enrich company data with comprehensive business intelligence from ZoomInfo's database. Provides detailed company profiles including business overview, financial data, contact information, corporate structure, and market intelligence.

SINGLE COMPANY ENRICHMENT:

enrich_company({
  "companies": [{ "domain": "https://company.com" }]
})

BATCH COMPANY ENRICHMENT:

enrich_company({
  "companies": [
    {"domain": "https://company1.com"},
    {"companyId": "12345"},
    {"companyName": "Tech Corp Inc"}
  ]
})

SUPPORTED IDENTIFICATION METHODS: For each company, provide at least one of these: • companyId (most accurate) • companyName • companyWebsite OR domain • companyTicker • Address information (street, city, state, etc.) • ipAddress

BATCH BENEFITS: • Process up to 10 companies in one API call • Faster execution for multiple enrichments • Organized results with individual company responses • Efficient for company list enrichment workflows

🔁 Chaining from a Search - "Get the full profile for a company I found":

For the query "Find fintech companies in NYC and give me the full profile on the top one", chain a search with an enrichment:

1. Call search_companies with your filters to find matching companies and their companyIds. 2. Call enrich_company with the companyId of the company you want full details on.

Example Workflow:

1. Call the industries lookup tool with fieldName: "industries" to find the exact id for the desired industry (e.g., "software.fintech").
2. search_companies(industryList: ["<industry_id>"], metroRegion: "NY
- New York City") → Returns companies with companyId: 55555, 66666, ...
3. enrich_company({ "companies": [{ "companyId": "55555" }], "requiredFields": ["revenue", "employeeCount", "companyFunding", "website"] }) → Returns full profile

CREDITS: This tool consumes ZoomInfo Bulk Credits. Once a company is enriched using this tool or on ZoomInfo's platform, subsequent enrichments of the company will not consume credits for one year from the first enrichment.

Parameters (1 required, 2 optional)
Required
companiesarray

Array of companies to enrich. Each company must have at least one valid identification method.

Optional
requiredFieldsarray

List of fields that will be returned by the enrichment. Specify which fields should be returned in the enriched result. If none are specified, the default fields returned are: name, description, city, state, country, revenue, and industries. Available fields: • socialMediaUrls - Social media URLs associated with the company • primaryIndustry - Company's primary industry classification • primaryIndustryCode - Code for the company's primary industry • primarySubIndustryCode - Code for the company's primary sub-industry • industries - List of all industries the company operates in • industryCodes - Industry classification codes • website - Company's website URL • type - Company type (e.g., Public, Private, Non-Profit) • ticker - Stock ticker symbol for publicly traded companies • name - Company name • description - Company description and business overview • phone - Company's primary phone number • street - Street address of company headquarters • city - City of company headquarters • state - State or province of company headquarters • zipCode - Zip or postal code of company headquarters • country - Country of company headquarters • continent - Continent where company headquarters is located • logo - Company logo URL • employeeCount - Total number of employees • employeeRange - Employee count range (e.g., 50-100, 100-500) • revenueRange - Revenue range classification • domainList - List of domains associated with the company • revenue - Annual revenue amount • numberOfContactsInZoomInfo - Number of contacts available in ZoomInfo database • companyStatus - Current operational status of the company • companyStatusDate - Date when the company status was last updated • ultimateParentId - ZoomInfo ID of the ultimate parent company • ultimateParentName - Name of the ultimate parent company • ultimateParentRevenue - Annual revenue of the ultimate parent company • ultimateParentEmployees - Total employees of the ultimate parent company • subUnitType - Type of organizational sub-unit (e.g., Headquarters, Branch, Subsidiary) • subUnitIndustries - Industries associated with this sub-unit • parentId - ZoomInfo ID of the immediate parent company • parentName - Name of the immediate parent company • locationCount - Number of company locations/offices • locationMatch - Indicates if the provided location matches the company's primary address • metroArea - Metropolitan area where the company is located • lastUpdatedDate - Date when the company information was last updated • createdDate - Date when the company record was created in ZoomInfo • certificationDate - Date when the company data was certified • certified - Indicates if the company data has been certified • companyFunding - Company funding information and funding rounds • recentFundingAmount - Amount of the most recent funding round • recentFundingDate - Date of the most recent funding round • totalFundingAmount - Total amount of funding raised across all rounds • foundedYear - Year the company was founded • businessModel - Company's business model (e.g., B2B, B2C, B2B2C) • isDefunct - Indicates if the company is no longer operating • departmentBudgets - Budget information by department • employeeCountByDepartment - Employee headcount broken down by department

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Enrich Company Signals

enrich_company_signals
Full Description

Fetch multiple signal types for specific companies in a single request, enriching company details with Intent, News, and Scoops data.

Required: Each request must include at least one zoominfoCompanyId and can enrich up to 10 companies at once.

Key Parameters: • zoominfoCompanyIds

  • Array of ZoomInfo company IDs (1-10 company Ids per request)

• signalTypes

  • Optional filter to specify which signals to return (INTENT, NEWS, SCOOP). If omitted, all three signal types are returned and sorted by latest date.

Example: "Get all signals for two companies":

enrichCompanySignals(zoominfoCompanyIds: [123456789, 987654321])

Example: "Get only Intent and News signals for a company":

enrichCompanySignals(zoominfoCompanyIds: [123456789], signalTypes: ["INTENT", "NEWS"])

Use Cases: This unified endpoint gets the latest signals (intents, news, scoops) across multiple categories for a company in a single request, so it is ideal for getting a comprehensive picture of what's been happening with the company recently. Example questions:

  • What solutions is this account searching for right now?
  • What news has been published about them recently?
  • What are some recent big company changes?

Credit Usage: This endpoint Charges data credits for any records returned for companies not currently under management. Companies enriched within the prior 12 months do not incur additional charges. It charges credits for each company enriched. Each signal (Intent, News, or Scoop) returned in the results counts as a Record, and a successful response counts as a Request credit.

Parameters (1 required, 2 optional)
Required
zoominfoCompanyIdsarray

Array of companyIds to enrich.

Optional
signalTypesarray

Indicates which signals to return. If not specified, all three signals will be returned. **Signal Types:** **INTENT** - What the company is actively researching. Behavioral signal derived from search and content consumption. Predictive of buying interest. **NEWS** - External press coverage, or third-party narrative about the company. Includes earnings, funding, M&A, executive moves, and product launches. **SCOOP** - Discrete business events curated from multiple sources. Specific moments such as executive moves, funding rounds, partnerships, layoffs, expansions, and earnings.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Enrich Contacts

enrich_contacts
Full Description

Enrich contacts data with verified business information from ZoomInfo's database. All data returned by this tool is strictly business-related — including corporate email addresses, business phone numbers, job details, company data, and professional network information. This tool does not return personal contact information such as private phone numbers, personal email addresses, or non-professional data of any kind.

SINGLE CONTACT ENRICHMENT:

enrich_contact({
  "email": "john.smith@company.com"
})

BATCH CONTACT ENRICHMENT:

enrich_contact({
  "contacts": [
    {"email": "john.smith@company.com"},
    {"personId": "12345"},
    {"firstName": "Jane", "lastName": "Doe", "companyName": "Tech Corp"}
  ]
})

SUPPORTED IDENTIFICATION METHODS: For each contact, provide one of these valid combinations: • personId (most accurate) • email • phone • (firstName AND lastName AND companyName) • (fullName AND companyName) • (firstName AND lastName AND companyId) • (fullName AND companyId)

BATCH BENEFITS: • Process up to 10 contacts in one API call • Faster execution for multiple enrichments • Organized results with individual contact responses • Efficient for lead list enrichment workflows

CREDITS: This tool consumes ZoomInfo Bulk Credits. Once a contact is enriched using this tool or on ZoomInfo's platform, subsequent enrichments of the contact will not consume credits for one year from the first enrichment.

Parameters (1 required, 2 optional)
Required
contactsarray

Array of contacts to enrich. Each contact must have at least one valid identification method.

Optional
requiredFieldsarray

List of fields that will be returned by the enrichment. Specify which fields should be returned in the enriched result. If none are specified, the default fields returned are: firstName, lastName, email, companyId, and companyName. Available fields: • companyName - The name of the company this contact is employed by • contactAccuracyScore - This score indicates the likelihood that a contact is reachable and still employed by the company listed • directPhoneDoNotCall - Direct phone Do Not Call status • education - Contact's education history; each entry includes the school attended, area of study, and degree earned, as applicable • email - Contact's verified business email address (corporate domain only; personal emails such as Gmail or Yahoo are not returned) • employmentHistory - Contact's employment history • externalUrls - External URLs for the contact's professional profiles (e.g., LinkedIn); personal or non-professional websites are not included • firstName - Contact's first name • jobFunction - Contact's job function • jobTitle - Contact's job title • lastName - Contact's last name • lastUpdatedDate - Date when the contact information was last updated • managementLevel - Contact's management level • mobilePhone - Contact's business mobile phone number (professionally verified work mobile, not a personal mobile) • mobilePhoneDoNotCall - Mobile phone Do Not Call status • phone - Contact's business direct-dial phone number (professionally verified work number, not a personal phone) • picture - Contact's profile picture URL • positionStartDate - Date when the contact started their current position • salutation - Contact's salutation (e.g., Mr., Ms., Dr.) • suffix - Contact's name suffix (e.g., Jr., Sr., III) • validDate - Date when the contact information was last validated • withinCalifornia - Indicates if the contact is within California • withinCanada - Indicates if the contact is within Canada • withinEu - Indicates if the contact is within the European Union • yearsOfExperience - Contact's years of professional experience • zoominfoCompanyId - ZoomInfo company ID associated with this contact's employer

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Enrich Intent

enrich_intent
Full Description

Fetch Intent Signals for a specific company, enriching that company's details with relevant buyer intent data.

Required: Each request must include at least one company identifier (companyId, companyName, or companyWebsite) and at least 1 and up to 50 intent topics.

Key Terminology: • Topic

  • A business subject or technology area mapped to a curated collection of keywords and search terms. When companies research content containing these keywords, it generates intent signals that indicate their buying interest

• Signal Score

  • Indicates the level of a company's interest in a topic (60-100) based on how recent content consumption compares to an historical baseline

• Audience Strength

  • Indicates the size of the group at the company that is conducting the research (A=largest audience, E=smallest)

🔍 **Recommended Workflow

  • Using Lookup for Accurate Results:**

For intent enrichment with specific topics, you should:

1. Call lookup with fields: [{ fieldName: "intent-topics" }] to get standardized topic values 2. Call enrich_intent with exact topic names from lookup results and company identifier

Example: "Find ZoomInfo's intent signals for Cloud Applications and Java":

1. lookup(fields: [{ fieldName: "intent-topics", fuzzyMatch: "cloud" }, { fieldName: "intent-topics", fuzzyMatch: "java" }])
   → Returns topics: ["Cloud Applications", "Java", ...]
2. enrich_intent(companyName: "ZoomInfo", topics: ["Cloud Applications", "Java"], signalScoreMin: 70)

Use Enrich Intent to find Intent Signals for a specific company. To search Intent Signals across all ZoomInfo companies, use the Search Intent endpoint.

CREDITS: This endpoint charges a single credit for the company being enriched. Each Intent Signal returned in the results is counted as a Record, and a successful response counts as a Request credit.

Parameters (0 required, 15 optional)
Optional
audienceStrengthMaxstring

Maximum audience strength. Values: A, B, C, D, E — A indicates the largest audience and the highest maximum strength. Use with audienceStrengthMin to set a range where audienceStrengthMax must be closer to A than audienceStrengthMin. For example, audienceStrengthMax: B and audienceStrengthMin: D will return results with audience strength of B, C, or D but not E.

Options:ABCDE
audienceStrengthMinstring

Minimum audience strength. Values: A, B, C, D, E — E indicates the smallest audience and the lowest minimum strength. Use with audienceStrengthMax to set a range.

Options:ABCDE
companyIdstring

Unique ZoomInfo identifier for a company (most accurate for enrichment)

companyNamestring

Company name

companyWebsitestring

Company website URL in https://www.example.com format

findRecommendedContactsboolean

Whether to include recommended contacts in results. Can include a large amount of contact data and lead to timeouts, so use with caution. Default: false. Set to true to include

pageinteger

Page number for pagination

pageSizeinteger

Number of results per page

signalEndDatestring

End date for a company signaling interest in a topic. Uses YYYY-MM-DD format.

signalScoreMaxinteger

Maximum signal score. Use with signalScoreMin to form a range. Minimum score is 60 and maximum is 100.

signalScoreMininteger

Minimum signal score. Use with signalScoreMax to form a range. Minimum score is 60 and maximum is 100.

signalStartDatestring

Start date for a company signaling interest in a topic. Uses YYYY-MM-DD format.

sortstring

Sort field for results. Use minus sign prefix for descending order.

Options:-audienceStrength-category-companyName-signalDate-signalScore-topicaudienceStrengthcategorycompanyNamesignalDatesignalScoretopic
topicsarray

Intent topic names. Accepts an Array of up to 50 topic name Strings. Use the lookup tool with fieldName: 'intent-topics' to get valid topic names. If empty or not provided, all configured topics (up to 50) will be used.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Enrich News

enrich_news
Full Description

Fetch News articles for a specific company, enriching that company's details with relevant news coverage.

Required: Each request must include company identifier (zoominfoCompanyId).

For news enrichment filtered by specific categories, pass one or more NewsCategoryEnum values to the categories field.

Example: "Find ZoomInfo's recent product news":

enrich_news(zoominfoCompanyId: 123123123, categories: ["PRODUCT"], publishingDateStart: "2026-01-01")

Credit Usage: This endpoint charges a single credit for the enriched company. Each News article returned in the results is counted as a Record, and a successful response counts as a Request credit. For example, a successful response that returns 10 news articles, 1 credit will be charged if applicable, 10 Records will be counted, and 1 Request will be counted.

Parameters (1 required, 7 optional)
Required
zoominfoCompanyIdinteger

Unique ZoomInfo identifier for a company

Optional
articleUrlsarray

News article URLs to filter by. Minimum of 5 characters per URL.

categoriesarray

Category of news articles to filter by. Valid values: - FINANCIAL_RESULTS: Earnings reports, revenue announcements, financial performance - FUNDING: Investment rounds, venture capital, debt financing - GENERAL_NEWS: Broad news coverage about a company - GENERAL_PRESS_RELEASE: Official company press releases - MERGER_OR_ACQUISITION: M&A activity, acquisitions, mergers - PERSON: Executive moves, leadership changes, appointments - PRODUCT: Product launches, updates, new releases

pageinteger

Page number for pagination

pageSizeinteger

Number of results per page

publishingDateEndstring

Latest publishing date for news articles. Uses YYYY-MM-DD format.

publishingDateStartstring

Earliest publishing date for news articles. Uses YYYY-MM-DD format.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Enrich Scoops

enrich_scoops
Full Description

Enrich the specified company with relevant Scoops. A company identifier must be provided (zoominfoCompanyIds, companyName, or companyWebsites); all other criteria are optional.

KEY PARAMETERS: • zoominfoCompanyIds

  • ZoomInfo unique identifiers for the company (most accurate)

• companyName

  • Company name

• companyWebsites

  • Company website URLs in https://www.example.com format

OPTIONAL FILTERS: • scoopIds

  • ZoomInfo unique identifiers for Scoops

• scoopTypes

  • Retrieve scoops based on type (e.g. Earnings, Award, and Partnership).

• scoopTopics

  • Retrieve scoops based on topic (e.g. integration, consolidation and compliance). Accepts a list of IDs from the lookup tool

• department

  • Retrieve scoops based on department (Information Technology, Finance, Human Resources and so on).

• description

  • Search for scoops based on description. Accepts a space-separated list of individual words

• publishedStartDate

  • Starting date to search for scoops based on publication date (YYYY-MM-DD format)

• publishedEndDate

  • Ending date to search for scoops based on publication date (YYYY-MM-DD format)

• updatedSinceCreation

  • Default is false. Setting true will only return scoops that have been updated since publishedStartDate

USE CASES: Scoop data can be used to:

  • Identify timely business events and trigger outreach based on company news
  • Track company changes such as leadership moves, expansions, and partnerships
  • Prioritize accounts based on recent activity signals
  • Personalize outreach with relevant, up-to-date company context

CREDIT USAGE: With reference to ZoomInfo's Credit Usage and Limits, a credit will be counted for the enriched company. Each Scoop returned in the results counts towards the customer's Record limit and a successful response will count towards the Request limit.

Parameters (0 required, 15 optional)
Optional
companyNamestring

Company name.

companyWebsitesarray

Company website URLs in https://www.example.com format.

departmentarray

Retrieve scoops based on department (IT, finance, HR and so on).

descriptionstring

Search for scoops based on description. Accepts a space-separated list of individual words.

pageinteger

Page number for pagination

pageSizeinteger

Number of results per page

publishedEndDatestring

Ending date to search for scoops based on publication date. Form a range using publishedStartDate. Uses YYYY-MM-DD format.

publishedStartDatestring

Starting date to search for scoops based on publication date. Form a range using publishedEndDate or omit publishedEndDate to search to the current date. Uses YYYY-MM-DD format.

scoopIdsarray

ZoomInfo unique identifiers for Scoops.

scoopTopicsarray

Retrieve scoops based on topic (e.g. integration, consolidation and compliance). Accepts a list of IDs from the lookup tool.

scoopTypesarray

Retrieve scoops based on type.

sortstring

Sort results by valid output fields. Default is -originalPublishedDate.

Options:scoopId-scoopIdoriginalPublishedDate-originalPublishedDatedescription-descriptionlink-linklinkText-linkText
updatedSinceCreationboolean

Default is false. Setting true will only return scoops that have been updated since publishedStartDate.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zoominfoCompanyIdsarray

ZoomInfo unique identifiers for the company.

Find Similar Companies

find_similar_companies
Full Description

Use this tool to find similar companies for a given reference company.

Required: Either zoominfoCompanyId or companyName must be provided. A request without one of these will fail with an error. The boolean filters alone are not sufficient to identify the reference company.

Required:

  • Provide either zoominfoCompanyId (preferred) or companyName. At least one is mandatory.

Optional:

  • sameRevenueRange, sameCountry, sameIndustry, sameEmployeeRange: boolean filters to narrow results to companies sharing that attribute with the reference company.
  • pageSize: number of results to return (default 25, max 100).

Similar companies can be used to retrieve a ranked list of companies that are similar to a given reference company. The similar companies are identified using a machine learning model that analyzes industry, revenue range, employee count, and other firmographic signals. These similar companies can be used to power prospecting, territory planning, or market expansion workflows where one wants to quickly find companies that "look like" a successful or high-priority account.

To find similar companies, provide the zoominfoCompanyId of the reference company, which identifies the company you want to use as the basis for finding similar companies. If zoominfoCompanyId is not provided, the tool will attempt to resolve the best matching company for the provided companyName and then return similar companies based on that company. The more precise the company name is (for example, use the full company name with correct spelling and full legal name), the more likely the service is able to track down the desired Company ID and use it to find similar companies.

Optionally, you can narrow the results using the following boolean filters. When set to true, each filter restricts similar companies to those that share the corresponding attribute with the reference company:

  • sameRevenueRange: same revenue range
  • sameCountry: same country
  • sameIndustry: same industry
  • sameEmployeeRange: same employee count range

Behind the scenes, the model uses a semantic vector representation of the reference company's data to efficiently find similar companies in the ZoomInfo database.

The tool returns up to 100 similar companies, ordered from the most similar company to the least similar company (descending order by similarity score attributes.score). To control the number of results returned, use the pageSize parameter with any integer value between 1 and 100 (default 25).

Each result includes the company name, similarity score, rank, and key firmographic attributes such as industry, revenue range, employee range, and country.

WORKFLOW: 1. Use the Find Similar Companies tool to retrieve similar companies. If the company name is provided but not the Company ID, the tool will attempt to resolve the best matching company and then retrieve the Company ID. 2. OPTIONAL Use the enrich_companies tool to retrieve the company details. 3. OPTIONAL Use the company details retrieved in step 2 to enrich the results retrieved in step 1.

CREDITS: Free to use

Parameters (0 required, 9 optional)
Optional
companyIdstring

DEPRECATED for zoominfoCompanyId

companyNamestring

Name of the reference company used to retrieve similar companies. Either companyName or zoominfoCompanyId must be provided.

pageSizeinteger

Number of records to return per page. Default is 25, maximum is 100.

sameCountryboolean

When true, restricts results to companies in the same country as the reference company.

sameEmployeeRangeboolean

When true, restricts results to companies within the same employee count range as the reference company.

sameIndustryboolean

When true, restricts results to companies in the same industry as the reference company.

sameRevenueRangeboolean

When true, restricts results to companies within the same revenue range as the reference company.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zoominfoCompanyIdinteger

Unique ZoomInfo identifier for the reference company used to retrieve similar companies. It is NOT a salesforce or CRM ID. e.g. '12345678' or '-43211234', but not '0011U00000adQbXQAU'. Either zoominfoCompanyId or companyName must be provided.

Find Similar Contacts

find_similar_contacts
Full Description

Use this tool to retrieve a ranked list of top N similar contacts for a reference person, optionally constrained to a target company. Required:

  • referencePersonId: Unique identifier for the reference person (ZoomInfo Person ID) used to search similar contacts.

Optional:

  • targetCompanyId: Unique identifier (ZoomInfo Company ID) for the target company where similar contacts are searched. If not provided, the model searches across all companies.

Similar contacts can be used to retrieve a ranked list of people who are most similar to a given reference person. The recommendations are generated by a machine learning model that compares the reference person's profile to other contacts. The profile includes person characteristics such as title, seniority, department, job function, as well as company characteristics such as industry and company size. These similar contacts can be used to identify additional stakeholders, expand buyer networks, or build targeted prospecting lists based on known high-priority contacts. Important: This tool is designed for legitimate business research. Users are responsible for compliance with applicable privacy laws (GDPR, CCPA, CAN-SPAM).

To find similar contacts, select the referencePersonId, which identifies the person whose profile you want to use as the basis for finding similar contacts. You can optionally provide a targetCompanyId to constrain the search to a specific company. If targetCompanyId is not provided, the model will search for similar contacts across all companies in the Zoominfo database.

Behind the scenes, the model uses a semantic vector representation of the reference person's profile to efficiently find similar contact profiles in the ZoomInfo database. It then applies a re-ranking algorithm to the set of similar contacts found, in order to boost relevance in the final return list.

The tool returns up to 100 similar contacts, ORDERED FROM MOST TO LEAST RELEVANT. Each similar contact contains additional metadata (meta) that describes the reference person used to form the similar contact. PLEASE USE THIS METADATA TO EXPLAIN WHY THE SIMILAR CONTACT WAS RECOMMENDED.

IMPORTANT CONTEXT

  • This tool is for finding similar contacts for a contact, not for an account. For accounts, use the get_account_lookalikes tool.

WORKFLOW: 1. If the user provided a company name as a target but does not provide a Company Id, use the search_companies tool to retrieve the Company ID of the target company name. 2. If the user provided a reference person name but does not provide a Person ID, use the search_contacts tool to retrieve the Person ID of the reference person name. 3. Use the Find Similar Contacts tool to retrieve similar contacts. 4. OPTIONAL Use the enrich_contacts tool to retrieve the contact details. 5. OPTIONAL Use the contact details retrieved in step 4 and combine with the metadata retrieved in step 3 to identify appropriate business contacts for research and strategic planning purposes.

COMMON USE CASES:

  • Show me contacts similar to John Smith in Microsoft. Followup: What makes Alex Johnson a lookalike of John Smith?
  • Show me contacts that look like John Smith across my org.

CREDITS: Free to use

Parameters (1 required, 3 optional)
Required
referencePersonIdinteger

Unique identifier for the reference person (ZoomInfo Person ID) that is used to search similar contacts. Example: * If a `referencePersonId` pointing to a person in Microsoft is provided, and if Apple's Zoominfo Company ID is provided as `targetCompanyId`, the endpoint will search for contacts within Apple that have similar persona attributes to this reference person from Microsoft. * Using the same example but if `targetCompanyId` **IS NOT** provided, the endpoint will search for contacts across all companies with similar persona attributes to the reference person from Microsoft.

Optional
pageSizeinteger

Number of records to return per page. Default is 25, maximum is 100.

Default: 25
targetCompanyIdinteger

Unique identifier (ZoomInfo Company ID) for the target company where similar contacts are searched. If not provided, the model searches across all companies. Example: * If Apple's Zoominfo Company ID is provided, the endpoint will search for contacts within Apple that have similar persona attributes to the provided `referencePersonId`. * If `targetCompanyId` **IS NOT** provided, the endpoint will search for contacts across all companies with similar persona attributes to the reference person from Microsoft.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Get Audience

get_audience
Full Description

Fetch detailed data for a specific GTM Studio audience, including column definitions and an optional row preview. Use audience IDs from page context, browseAudiences, or upsertAudience; never generate or guess. For audienceAnalysis, use the returned audience ID as audienceId. Set previewRows to true to include row preview data; by default, 5 rows are returned unless previewRowLimit is provided. Use previewRowLimit (max 25) to control row preview size and previewColumnIds to scope preview columns.

Parameters (1 required, 5 optional)
Required
audienceIdstring

UUID of the audience to fetch. Required. Use audience IDs from page context, browseAudiences, or upsertAudience; never generate or guess.

Optional
previewColumnIdsarray

Optional subset of column IDs to include in preview rows. Only applicable when `previewRows` is true; ignored otherwise. If omitted, all columns are included.

previewRowLimitinteger

Optional maximum number of preview rows to include in the response. Only applicable when `previewRows` is true; ignored otherwise. Minimum is 1 and maximum is 25. If omitted, defaults to 5 when previewRows is true.

previewRowsboolean

Whether to include a preview of row data in the response. Defaults to false.

rowFilterobject

Optional filter to narrow which rows are included in the preview. Only applicable when `previewRows` is true; ignored otherwise.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

GTM Context

get_gtm_context
Full Description

Returns the authenticated user's GTM context: their role, what their organization offers (products and services), ideal customer profiles, buyer personas, competitors, and strategic priorities. No parameters required — identity is resolved from authentication. This is read-only; the user needs admin permissions to create, update, delete or archive configuration. No ZoomInfo credits consumed. This context shapes how other ZoomInfo tools deliver value. Search, enrichment, and prospecting results are more relevant when filtered and scored against the user's ideal customer profiles, buyer personas, and competitive landscape. Without it, those tools return unqualified results that require manual assessment. Compressed by default (~1,000 tokens). Use detailed=true for expanded profiles. Each entity includes a status field ('active' or 'archived') and an archivedAt timestamp when applicable, so archived configuration is always visible.

Parameters (0 required, 2 optional)
Optional
detailedboolean

When true, the tool returns the full profiles for all records. Defaults to false.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Get Recommended Contacts

get_recommended_contacts
Full Description

Use this tool to retrieve a ranked list of top N contact recommendations at a target company based on the users interaction history. Required:

  • Company ID to search with. If you don't have this yet, use the search_companies tool set first.
  • Use case type for the recommendation. This filters recommendations based on the sales motion, depending on use case, it can the following:
    • PROSPECTING (capitalized): for recommendations based on similar contacts to those copied, viewed, or exported by the user on the ZoomInfo Platform. The prospecting use-case has cold-start support; when in doubt default to this use case.
    • DEAL_ACCELERATION: when the use-case calls for recommending contacts similar to those in the set of closed won opportunities in user's tenant's CRM for new business initiatives.
    • RENEWAL_AND_GROWTH: when the use-case calls for recommending contacts similar to those in the set of closed won opportunities in user's tenant's CRM for renewal initiatives.

Contact Recommendations can be used to retrieve a ranked list of people at a target company who are most relevant for a given sales motion (use case), such as prospecting, deal acceleration, or renewal and growth. The recommendations are derived from past user interactions and account activity, and are ranked by a machine learning model. These recommendations can be used to identify appropriate business contacts for research and strategic planning purposes. Compliance Note: Search results are intended for professional research. Ensure all use aligns with your organization's data governance policies.

Behind the scenes, the model leverages data such as the user's past contact views, exports, and copies for the PROSPECTING motion, or contacts from a user's CRM related to closed won deals for the DEAL_ACCELERATION motion. The model uses this data to infer which types of people are most likely to drive success for the selected motion. It then finds similar contacts at the target company and scores them using a combination of similarity and propensity signals.

The tool returns up to 100 recommended contacts, ORDERED FROM MOST TO LEAST RELEVANT. Each recommendation contains additional metadata (meta) that describes the reference person used to form the recommendation. PLEASE USE THIS METADATA TO EXPLAIN WHY THE RECOMMENDED PERSON WAS RECOMMENDED.

Each recommendation includes the general similarity score (score), and the re-ranking score (reRankingScore) which uses several propensity signals (such as contact similarity, contact quality, title boosting, etc.) to refine relevancy. Note that reRankingScore returns -1.0 when the ML reranking model did not run.

IMPORTANT CONTEXT:

  • The score and reRankingScore are not directly comparable. The score is a general similarity score, while the reRankingScore is a re-ranking score that uses several propensity signals (such as user platform interactions, contact similarity, contact quality, title boosting, etc.)

to refine relevancy. A reRankingScore of -1.0 indicates the reranking model did not run.

  • The contact recommendations are updated daily.
  • The contact recommendations are powered by list engagement, CRM data, and propensity signals.
  • Higher scores does not guarantee responses.

WORKFLOW: 1. Use the search_companies tool to retrieve the Company ID of the target company name, if the Company ID is not provided. 2. Use the Get Contact Recommendations tool to retrieve the contact recommendations. 3. OPTIONAL Use the enrich_contacts tool to retrieve the contact details. 4. OPTIONAL Use the contact details retrieved in step 3 and combine with the metadata retrieved in step 2 to identify appropriate business contacts for research and strategic planning purposes.

COMMON USE CASES:

  • Who are the top 10 people to reach out to at Microsoft? (for prospecting)
  • Who are the top 5 people to reach out to at Apple based on similar successful past deals?
  • Why is this person recommended for my use case?

CREDITS: Free to use

Parameters (2 required, 2 optional)
Required
useCaseTypestring

Use case type for the recommendation. This filters recommendations based on the sales motion, such as prospecting, deal acceleration, or renewal and growth.

Options:PROSPECTINGDEAL_ACCELERATIONRENEWAL_AND_GROWTH
ziCompanyIdinteger

Unique identifier for a target company (ZoomInfo Company ID) in which to get contact recommendations.

Optional
pageSizeinteger

Number of records to return per page. Default is 25, maximum is 100.

Default: 25
userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

Lookup

lookup
Full Description

Lookup reference data

  • This tool provides standardized parameter values for use in search operations. Using lookup helps ensure accurate search results.

Note: Use the id field, not attributes.name • Lookup results contain both id and attributes.name • Use the id value in search parameters • The attributes.name is for human readability only • Example: Use id: "12345" not attributes.name: "Vice President"

Recommended Workflow: 1. Call lookup to get exact field values 2. Extract the id field from each result 3. Use the id values in search_contacts or search_companies 4. This helps prevent search failures and ensures accurate results

Single field lookup:

lookup(fields: [{ fieldName: "management-levels" }]) → Get VP options, use result.id

Multiple fields lookup:

lookup(fields: [{ fieldName: "management-levels" }, { fieldName: "metro-regions" }, { fieldName: "industries" }, { fieldName: "employee-count" }]) → Get all options, use result.id values

Fuzzy match filtering:

lookup(fields: [{ fieldName: "tech-vendors", fuzzyMatch: "hubspot" }]) → Returns vendors matching "hubspot", use result.id (e.g., "HubSpot, Inc")
lookup(fields: [{ fieldName: "industries", fuzzyMatch: "software" }]) → Returns industries containing "software", use result.id

• Use fuzzyMatch within each field object to filter results by partial name match (case-insensitive) • Helps find specific items when you don't know the exact name • Example: searching "hub spot" will match "HubSpot, Inc"

Note: For batch lookups with multiple fields, pass each as a separate object in the fields array.

  • Per-field fuzzyMatch is set on each field object individually (e.g., [{ fieldName: "metro-regions", fuzzyMatch: "boston" }, { fieldName: "industries" }] filters field 1, not field 2)
  • Omit fuzzyMatch or set it to null to skip filtering for a specific field

Example: VP-level tech contacts in San Francisco (100-500 employees):

Step 1: lookup(fields: [{ fieldName: "management-levels" }, { fieldName: "metro-regions", fuzzyMatch: "san francisco" }, { fieldName: "industries", fuzzyMatch: "software" }, { fieldName: "employee-count" }]) → Get all options at once
Step 2: Extract id values from results
Step 3: search_contacts(managementLevel: "<id>", metroRegion: "<id>", industryCodes: "<id>", employeeCount: "<id>")

Example: Companies using specific technology (e.g., "Companies in Boston using HubSpot"):

Step 1: lookup(fields: [{ fieldName: "tech-vendors", fuzzyMatch: "hubspot" }]) → Get vendor id
Step 2: lookup(fields: [{ fieldName: "tech-products" }], vendor: "<vendor_id>") → Get HubSpot product ids
Step 3: lookup(fields: [{ fieldName: "metro-regions", fuzzyMatch: "boston" }]) → Get metro id
Step 4: search_companies(techAttributeTagList: "<product_ids>", metroRegion: "<metro_id>")

Note: For technology searches, lookup tech-vendors (with fuzzyMatch), then lookup tech-products (with vendor parameter), and use the id values.

Common lookup fields: • management-levels

  • VP, Director, C-Level classifications (for seniority searches)

• metro-regions

  • Exact metropolitan area names (for location searches)

• industries

  • Industry classifications (for sector searches)

• employee-count

  • Company size ranges (for size filters)

• job-functions

  • Job function categories

• departments

  • Department classifications

• company-types

  • Public/private classifications

• revenue-ranges

  • Revenue classifications

• funding-round-types

  • Funding round classifications (e.g., Seed, Series A) for recentFundingRoundTypes/allFundingRoundTypes filters

• tech-vendors

  • Technology vendor names (use fuzzyMatch for partial matching, use before tech-products lookup)

• tech-products

  • Technology product IDs (use vendor parameter with exact vendor name from tech-vendors lookup)

• tech-categories

  • Technology categories for broader tech stack searches

Note: Search tools may fail if you use incorrect field values. Consider using lookup and the id field for accuracy.

Note: When looking up hashtags and intent-topics, this tool will return a maximum of 100 records. If more than 100 records exist, the response will include a truncation notice indicating that results were limited.

CREDITS: Free to use

Parameters (1 required, 5 optional)
Required
fieldsarray

Array of lookup field objects to retrieve data for.

Optional
categorystring

Filter by category. Only applicable for hashtag lookups (e.g., "Unified Communications"). Used to narrow down results within a specific category.

parentCategorystring

Filter by parent category. Only applicable for hashtag and tech lookups (e.g., "Communication and Collaboration"). Used to filter results by parent category hierarchy.

subCategorystring

Filter by sub-category. Only applicable for hashtag and tech lookups (e.g., "Unified Communications as a Service"). Used to filter results by sub-category within the hierarchy.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

vendorstring

Filter by vendor name. Only applicable for hashtag and tech lookups (e.g., "microsoft corporation"). Used to filter results by specific vendor or company. For tech-products, use the exact vendor name returned from tech-vendors lookup.

Search Companies

search_companies
Full Description

Search for companies in ZoomInfo's comprehensive business database. Find companies by name, domain, industry, location, employee count, revenue, growth metrics, funding information, and advanced business criteria.

Several parameters have *List variants (e.g. companyTypeList, industryList, techAttributeTagIdList) that accept typed arrays instead of comma-separated strings — prefer these for new integrations, passing each value as a separate list item. The original comma-separated/singular parameters remain supported for backward compatibility.

🔍 **Recommended Workflow

  • Using Lookup for Accurate Results:**

For company searches with specific criteria, you can:

1. Call lookup with appropriate fieldNames to get standardized values 2. Call search_companies with exact values from lookup results

Example for "tech companies in San Francisco with 100–500 employees":

1. lookup(fields: [{ fieldName: "metro-regions", fuzzyMatch: "san francisco" }]) → Returns: "CA
- San Francisco"
2. lookup(fields: [{ fieldName: "industries", fuzzyMatch: "software" }]) → Returns: "Computer Software", "Information Technology Services"
3. search_companies(metroRegion: "CA
- San Francisco", industryList: ["software"], employeeRangeMinimum: 100, employeeRangeMaximum: 500)

Example for "Companies in Boston using HubSpot":

1. lookup(fields: [{ fieldName: "tech-vendors", fuzzyMatch: "hubspot" }]) → Returns vendor: "HubSpot, Inc"
2. lookup(fields: [{ fieldName: "tech-products" }], vendor: "HubSpot, Inc") → Returns HubSpot product IDs
3. lookup(fields: [{ fieldName: "metro-regions", fuzzyMatch: "boston" }]) → Returns: "MA
- Boston"
4. search_companies(techAttributeTagIdList: ["<product_id>"], metroRegion: "MA
- Boston")

Note: For technology stack searches, lookup tech-vendors first, then lookup tech-products with vendor parameter

Note: Using exact values returned by lookup tools helps ensure accurate search results. Guessing field values will cause search failures.

Consider using lookup for: • metro-regions (for location searches) • industries (for industry filters) • employee-count (for company size) • revenue-ranges (for revenue filters) • company-types (for public/private filters) • states/countries (for geographic searches) • tech-vendors → tech-products → techAttributeTagIdList (for technology stack searches)

CREDITS: Free to use

Parameters (0 required, 76 optional)
Optional
addressstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Street address

allFundingRoundTypesarray

Filters for companies that have had any funding round (at any point in their history) matching one of the given types. Accepts an array of values from the endpoint: /lookup/funding-round-types. This is a different filter mode than recentFundingRoundTypes (which matches only the most recent round), so only one of the two should be supplied per request.

businessModelarray

Search using Business Model (B2C, B2B, B2G) for a company. Default is All

certifiedinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Denotes if ZoomInfo's research and data team has confirmed activity within the past 12 months. 1 = certified, 0 = not certified

companyDescriptionstring

Search in company descriptions

companyIdstring

**Deprecated:** use `companyIdList` instead. Unique ZoomInfo identifier for the company

companyIdListarray

Unique ZoomInfo identifier for the company

companyNamestring

Company name

companyRankingstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company ranking lists (e.g., Fortune 500)

companyStructureIncludedSubUnitTypesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Include specific sub unit types in company structure

companyTickerarray

**Deprecated:** use `companyTickerList` instead. Company stock ticker symbols

companyTickerListarray

Company stock ticker symbols

companyTypestring

**Deprecated:** use `companyTypeList` instead. Company type (private, public, npo, education, government, other)

companyTypeListarray

Company type (private, public, npo, education, government, other)

companyWebsitestring

Company website URL in https://www.example.com format. Accepts a comma-separated list

continentstring

Continent name. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "continents" to get acceptable values. Combined with state, country, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

countrystring

Accepts a comma-separated list of countries. Use ZoomInfo lookup tool with fieldName: "countries" to get acceptable values. Combined with state, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

employeeCountstring

**Deprecated:** use `employeeRangeMinimum`/`employeeRangeMaximum` instead. Employee count range. Accepts a comma-separated list of values. Alternatively, for more granular ranges, you can use the employeeRangeMinimum and employeeRangeMaximum parameters. Valid values are: 1to4, 5to9, 10to19, 20to49, 50to99, 100to249, 250to499, 500to999, 1000to4999, 5000to9999, 10000plus Example: "10to19,50to99" will return companies with employee counts in either of those ranges.

employeeRangeMaxstring

**Deprecated:** use `employeeRangeMaximum` instead. Maximum employee count for a company. Accepts a single positive integer. Use with employeeRangeMin to set a range. Alternatively, you can use the employeeCount parameter to search for pre-defined ranges

employeeRangeMaximuminteger

Maximum employee count for a company. Must be greater than or equal to employeeRangeMinimum if present. Use with employeeRangeMinimum to set a range

employeeRangeMinstring

**Deprecated:** use `employeeRangeMinimum` instead. Minimum employee count for a company. Accepts a single positive integer. Use with employeeRangeMax to set a range. Alternatively, you can use the employeeCount parameter to search for pre-defined ranges

employeeRangeMinimuminteger

Minimum employee count for a company. Use with employeeRangeMaximum to set a range

engagementEndDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. End date for engagement tracking (YYYY-MM-DD)

engagementStartDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Start date for engagement tracking (YYYY-MM-DD)

engagementTypearray

**Deprecated:** retained for backward compatibility only; no longer actively supported. Types of engagement to track

excludeDefunctCompaniesboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Defaults to true. Set false to include defunct companies in results

excludedRegionsstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Regions to exclude from search

financeDepartmentBudgetMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum finance department budget

financeDepartmentBudgetMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum finance department budget

fundingAmountMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum funding amount received

fundingAmountMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum funding amount received

fundingEndDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. End date for funding period (YYYY-MM-DD)

fundingStartDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Start date for funding period (YYYY-MM-DD)

hashTagStringstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Hashtag-based search criteria. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "hashtags" to get acceptable values.

hrDepartmentBudgetMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum HR department budget

hrDepartmentBudgetMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum HR department budget

industryCodesstring

**Deprecated:** use `industryList` instead. Top-level industry that the contact works in. A contact can have multiple top level industries. Tags are based on the contact's current company. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "industries" to get acceptable values.

industryKeywordsstring

Industry keywords for broader matching

industryListarray

Top-level industry that the contact works in. Accepts a list of industry values. REQUIRED: You MUST call the lookup tool provided by this MCP server first with fieldName: "industries" and use ONLY the exact strings returned in the id field. "software.health", not "Healthcare Software". Passing any other value will cause an error.

itDepartmentBudgetMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum IT department budget

itDepartmentBudgetMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum IT department budget

locationSearchTypestring

Location type (PersonOrHQ, PersonAndHQ, Person, HQ, PersonThenHQ). When locationSearchType is passed in, a value must be provided for at least one of the following parameters: state, country, continent, metroRegion, zipCode, address.

Options:PersonOrHQPersonAndHQPersonHQPersonThenHQ
marketingDepartmentBudgetMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum marketing department budget

marketingDepartmentBudgetMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum marketing department budget

metroRegionstring

Company metro area. Accepts a comma-separated list of U.S. and Canada metro areas. Use ZoomInfo lookup tool with fieldName: "metro-regions" to get acceptable values. Combined with state, country, or continent using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

naicsCodesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. North American Industry Classification System codes. Accepts a comma-separated list from the lookup tool with fieldName: "naics-codes"

oneYearEmployeeGrowthRateMaxstring

**Deprecated:** use `oneYearEmployeeGrowthRateMaximum` instead. Maximum one-year employee growth rate percentage

oneYearEmployeeGrowthRateMaximumnumber

Maximum one-year employee growth rate. Use with oneYearEmployeeGrowthRateMinimum to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

oneYearEmployeeGrowthRateMinstring

**Deprecated:** use `oneYearEmployeeGrowthRateMinimum` instead. Minimum one-year employee growth rate percentage

oneYearEmployeeGrowthRateMinimumnumber

Minimum one-year employee growth rate. Use with oneYearEmployeeGrowthRateMaximum to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

pageinteger

Page number for pagination

Default: 1
pageSizeinteger

Number of results per page. Pagination caps at 10,000 total records.

Default: 25
parentIdstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Parent company ZoomInfo ID

primaryIndustriesOnlyboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Search only primary industries

recentFundingRoundTypesarray

Filters for companies whose most recent funding round matches one of the given types. Accepts an array of values from the endpoint: /lookup/funding-round-types. This is a different filter mode than allFundingRoundTypes (which matches any round in the company's history), so only one of the two should be supplied per request.

revenuestring

**Deprecated:** use `revenueMin`/`revenueMax` instead. Revenue range or specific amount

revenueMaxinteger

Maximum company revenue

revenueMininteger

Minimum company revenue

sicCodesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Standard Industrial Classification codes. Accepts a comma-separated list of values from the lookup tool with fieldName: "sic-codes"

sortstring

Sort field for results. Use minus sign prefix for descending order.

Options:-employeeCount-name-revenueemployeeCountnamerevenue
statestring

Accepts a comma-separated list of states or provinces from the U.S. and Canada. Use ZoomInfo lookup tool with fieldName: "states" to get acceptable values. Combined with country, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

streetstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Street address

subUnitTypesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company sub unit types (e.g., division, subsidiary)

techAttributeTagIdListarray

Technology Product Tags. Use values from the id field returned from ZoomInfo lookup tool with fieldName: "tech-products". First lookup tech-vendors with fuzzyMatch to find vendor, then lookup tech-products with vendor parameter.

techAttributeTagListstring

**Deprecated:** use `techAttributeTagIdList` instead. Technology Product Tags. Use values returned from ZoomInfo lookup tool with fieldName: "tech-products". First lookup tech-vendors with fuzzyMatch to find vendor, then lookup tech-products with vendor parameter. Can include a comma-separated list of product IDs.

twoYearEmployeeGrowthRateMaxstring

**Deprecated:** use `twoYearEmployeeGrowthRateMaximum` instead. Maximum two-year employee growth rate percentage

twoYearEmployeeGrowthRateMaximumnumber

Maximum two-year employee growth rate. Use with twoYearEmployeeGrowthRateMinimum to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

twoYearEmployeeGrowthRateMinstring

**Deprecated:** use `twoYearEmployeeGrowthRateMinimum` instead. Minimum two-year employee growth rate percentage

twoYearEmployeeGrowthRateMinimumnumber

Minimum two-year employee growth rate. Use with twoYearEmployeeGrowthRateMaximum to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

ultimateParentIdstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Ultimate parent company ZoomInfo ID

underManagementboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Filter by companies under management

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zipCodestring

Zip code or postal code. Unlike the other location fields (state, country, continent, metroRegion), which combine with each other using OR semantics (union), zipCode is intersected (AND semantics) with the combined result of all other supplied location fields, rather than being OR'd in as an additional branch of the union.

zipCodeRadiusMilesstring

Geographical radius (in miles) from the zipCode provided. Supported values: 10, 25, 50, 100, 250. The parameter zipCodeRadiusMiles requires that zipCode is non-null and valid.

Options:102550100250
zoominfoContactsMaxstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum number of ZoomInfo contacts at the company

zoominfoContactsMinstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum number of ZoomInfo contacts at the company

Search Contacts

search_contacts
Full Description

Search for business contacts in ZoomInfo's comprehensive database. Find professionals by name, company, job title, email, location, and advanced criteria including management level, department, contact accuracy scores, employment history, education, and extensive company attributes.

Several parameters have *List variants (e.g. jobTitleList, managementLevelList, industryList) that accept typed arrays instead of comma-separated strings — prefer these for new integrations, passing each value as a separate list item. The original comma-separated/singular parameters remain supported for backward compatibility.

🔍 **Recommended Workflow

  • Using Lookup for Accurate Results:**

For the query "Find all VP-level contacts at tech companies in San Francisco with 100–500 employees", you can:

1. Call lookup with fields: [{ fieldName: "management-levels" }] to get VP-level options 2. Call lookup with fields: [{ fieldName: "metro-regions", fuzzyMatch: "san francisco" }] to get San Francisco metro area name 3. Call lookup with fields: [{ fieldName: "industries", fuzzyMatch: "software" }] to get technology industry codes 4. Call lookup with fields: [{ fieldName: "employee-count" }] to get 100-500 employee range 5. Call search_contacts with the exact values from lookup results

Note: Using exact values returned by lookup tools helps ensure accurate search results. Guessing field values will cause search failures.

Example Workflow:

1. lookup(fields: [{ fieldName: "management-levels" }]) → Returns: "Vice President", "Senior Vice President", etc.
2. lookup(fields: [{ fieldName: "metro-regions", fuzzyMatch: "san francisco" }]) → Returns: "CA
- San Francisco"
3. lookup(fields: [{ fieldName: "industries", fuzzyMatch: "software" }]) → Returns: "Computer Software", "Information Technology Services", etc.
4. lookup(fields: [{ fieldName: "employee-count" }]) → Returns: "101-250", "251-500"
5. search_contacts(managementLevelList: ["VP Level Exec"], metroRegion: "CA
- San Francisco", industryList: ["software"], employeeRangeMinimum: 100, employeeRangeMaximum: 500)

Consider using lookup for: • management-levels (for VP, Director, C-Level searches) • metro-regions (for location-based searches) • industries (for industry-specific searches) • employee-count (for company size filters) • job-functions (for role-based searches) • departments (for department-specific searches)

CREDITS: Free to use

Parameters (0 required, 107 optional)
Optional
addressstring

Full Company Address

allFundingRoundTypesarray

Filters for companies that have had any funding round (at any point in their history) matching one of the given types. Accepts an array of values from the endpoint: /lookup/funding-round-types. This is a different filter mode than recentFundingRoundTypes (which matches only the most recent round), so only one of the two should be supplied per request.

boardMemberstring

Exclude or include board members from search results. Values: "include", "only", or exclude (default)

Options:includeexcludeonly
buyingGrouparray

**Deprecated:** use `buyingGroupId` instead. Filters results based on the provided Buying Group ID. Only one ID can be submitted

buyingGroupIdinteger

Filters results based on the provided Buying Group ID. Use ZoomInfo lookup tool with fieldName: "buying-groups" to get acceptable values.

companyDescriptionstring

Search for companies based on description. Accepts a space-separated list of individual words

companyIdstring

**Deprecated:** use `companyIdList` instead. Unique ZoomInfo identifier for the company, accepts a comma-separated list of IDs as strings

companyIdListarray

Unique ZoomInfo identifier for the company

companyNamestring

Company name

companyPastOrPresentstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company employment filter. Values: "present" (default), "past", "pastAndPresent"

Options:presentpastpastAndPresent
companyRankingstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company ranking (e.g., Fortune 500). Accepts a comma-separated list of IDs

companyStructureIncludedSubUnitTypesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company hierarchical structure values. Comma-separated list from UNSPECIFIED, LOCATION, DIVISION, ACQUISITION, SUBSIDIARY, FORMER_NEW_NAME

companyTickerarray

**Deprecated:** use `companyTickerList` instead. Company stock ticker symbols

companyTickerListarray

Company stock ticker symbols

companyTypestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company type (private, public, etc.). Accepts a comma-separated list of types Valid values are: none, private, public, npo, education, government, other. Example: "private,public" will return companies that are either private or public.

companyWebsitestring

Company website URL

contactAccuracyScoreMaxstring

**Deprecated:** use `contactAccuracyScoreMaximum` instead. Maximum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99

contactAccuracyScoreMaximuminteger

Maximum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99.

contactAccuracyScoreMinstring

**Deprecated:** use `contactAccuracyScoreMinimum` instead. Minimum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99

contactAccuracyScoreMinimuminteger

Minimum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99.

continentstring

Continent name. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "continents" to get acceptable values. Combined with state, country, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

countrystring

Accepts a comma-separated list of countries. Use ZoomInfo lookup tool with fieldName: "countries" to get acceptable values. Combined with state, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

degreestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Searches by contact's education

departmentstring

**Deprecated:** use `departmentList` instead. Contact department at current place of employment. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "departments" to get acceptable values.

departmentListarray

Contact department at current place of employment. REQUIRED: You MUST call the lookup tool provided by this MCP server first with fieldName: "departments" and use ONLY the exact strings returned in the name field. "Sales", "Marketing" not the id, "3". Passing any other value will cause an error.

emailAddressstring

Email address for the contact in example@example.com format

employeeCountstring

**Deprecated:** use `employeeRangeMinimum`/`employeeRangeMaximum` instead. Employee count range. Accepts a comma-separated list of values. Alternatively, for more granular ranges, you can use the employeeRangeMinimum and employeeRangeMaximum parameters. Valid values are: 1to4, 5to9, 10to19, 20to49, 50to99, 100to249, 250to499, 500to999, 1000to4999, 5000to9999, 10000plus Example: "10to19,50to99" will return companies with employee counts in either of those ranges.

employeeRangeMaxstring

**Deprecated:** use `employeeRangeMaximum` instead. Maximum employee count for a company. Accepts a single positive integer. Use with employeeRangeMin to set a range

employeeRangeMaximuminteger

Maximum employee count for a company. Must be greater than or equal to employeeRangeMinimum if present. Use with employeeRangeMinimum to set a range

employeeRangeMinstring

**Deprecated:** use `employeeRangeMinimum` instead. Minimum employee count for a company. Accepts a single positive integer. Use with employeeRangeMax to set a range

employeeRangeMinimuminteger

Minimum employee count for a company. Use with employeeRangeMaximum to set a range

engagementEndDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Engagement end date in YYYY-MM-DD format. EngagementStartDate is required

engagementStartDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Engagement start date in YYYY-MM-DD format

engagementTypearray

**Deprecated:** retained for backward compatibility only; no longer actively supported. List of engagement types to search for. Accepted values: email, phone, online meeting

exactJobTitlestring

**Deprecated:** use `jobTitleList` instead. Contact title using exact match logic. Use OR to input multiple job titles

excludedRegionsstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Comma-separated list of US States, Canadian Provinces, Countries and/or Continents to exclude

excludeJobTitlestring

**Deprecated:** use `excludeJobTitleList` instead. Comma-separated list of job titles to exclude from search results

excludeJobTitleListarray

List of job titles to exclude from search results. Do not exceed 500 total characters across all job titles.

excludeManagementLevelstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Comma-separated list of management levels to exclude from search results. Available values: "Board Member", "C Level Exec", "VP Level Exec", "Director", "Manager", "Non Manager". Example: "VP Level Exec,Non Manager"

excludePartialProfilesboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Defaults to false. To include partial profiles in your search results, set this to true. Contacts who do not have an active company associated with them are considered partial profiles

executivesOnlyboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Defaults to false. Set this to true to include only executives in search results

firstNamestring

Contact first name

fullNamestring

Contact full name

fundingAmountMaxinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum funding amount in thousands (e.g., 1 = 1000, 500 = 500,000)

fundingAmountMininteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum funding amount in thousands (e.g., 1 = 1000, 500 = 500,000)

fundingEndDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. End date of the funding in YYYY-MM-DD format

fundingStartDatestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Start date of the funding in YYYY-MM-DD format

hasBeenNotifiedstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Filter by notification status. Values: "include" (default), "exclude", "only"

hashedEmailstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Hashed email value for the contact. Supported hash algorithms: MD5, SHA1, SHA256, SHA512

hashTagStringstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Hash tags for a company. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "hashtags" to get acceptable values.

industryCodesstring

**Deprecated:** use `industryList` instead. Top-level industry that the contact works in. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "industries" to get acceptable values.

industryKeywordsstring

Industry keywords associated with a company. Can include either 'AND' or 'OR' operators

industryListarray

Top-level industry that the contact works in. Accepts a list of industry values. REQUIRED: You MUST call the lookup tool provided by this MCP server first with fieldName: "industries" and use ONLY the exact strings returned in the id field. "software.health", not "Healthcare Software". Passing any other value will cause an error.

jobFunctionstring

**Deprecated:** use `jobFunctionList` instead. Contact job function at their current place of employment. Accepts a comma-separated list of values.

jobFunctionListarray

Contact job function at their current place of employment. REQUIRED: You MUST call the lookup tool provided by this MCP server first with fieldName: "job-functions" and use ONLY the exact strings returned in the name field. "Sales Engineering", "Sales Enablement" not the id, "3.11".

jobTitlestring

**Deprecated:** use `jobTitleList` instead. Contact title at current place of employment. Not based on exact values from lookup tool. Use OR to input multiple job titles. Only allows letters and spaces, no special characters or numbers Example: "CFO OR Controller OR VP Finance OR Director Finance OR Treasurer OR VP Accounting OR Head of Procurement OR AP Manager OR VP Operations"

jobTitleListarray

Contact title at current place of employment. Not based on exact values from lookup tool. Only allows letters and spaces, no special characters or numbers. Do not exceed 500 total characters across all job titles. Example: ["CFO", "Controller", "VP Finance", "Director Finance", "Head of Procurement", "AP Manager", "VP Operations"]

lastNamestring

Contact last name

lastUpdatedDateAfterstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. The date after which the contact's profile was last updated (YYYY-MM-DD)

lastUpdatedInMonthsinteger

**Deprecated:** retained for backward compatibility only; no longer actively supported. Number of months within which the contact's profile was last updated

locationCompanyIdarray

**Deprecated:** retained for backward compatibility only; no longer actively supported. Searches by contact's location company IDs

locationSearchTypestring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Location type (PersonOrHQ, PersonAndHQ, Person, HQ, PersonThenHQ), HQ stands for headquarters. When locationSearchType is passed in, a value must be provided for at least one of the following parameters: state, country, continent, metroRegion, zipCode, address.

Options:PersonOrHQPersonAndHQPersonHQPersonThenHQ
managementLevelstring

**Deprecated:** use `managementLevelList` instead. Contact management level at current place of employment. Accepts a comma-separated list of values. Available values: "Board Member", "C Level Exec", "VP Level Exec", "Director", "Manager", "Non Manager". Example: "Director,Manager"

managementLevelListarray

Contact management level at current place of employment.

metroRegionstring

Company metro area. Accepts a comma-separated list of U.S. and Canada metro areas. Use ZoomInfo lookup tool with fieldName: "metro-regions" to get acceptable values. Combined with state, country, or continent using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

middleInitialstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Contact middle initial

naicsCodesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. North American Industry Classification System codes. Accepts a comma-separated list from the lookup tool with fieldName: "naics-codes"

oneYearEmployeeGrowthRateMaxstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum one year employee growth rate for a company

oneYearEmployeeGrowthRateMinstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum one year employee growth rate for a company

pageinteger

Page number for pagination

Default: 1
pageSizeinteger

Number of results per page. Pagination caps at 10,000 total records.

Default: 25
parentIdstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. ZoomInfo Company ID for parent company. Id must be an integer and cannot be zero

personIdstring

**Deprecated:** use `personIdList` instead. Unique ZoomInfo identifier for the contact. Can include a comma-separated list of integers as strings Example: "12345,67890"

personIdListarray

Unique ZoomInfo identifier for the contact Example: [12345,67890]

phonearray

**Deprecated:** retained for backward compatibility only; no longer actively supported. List of person phones or mobile numbers

positionStartDateMaxstring

Maximum date for when a contact began current employment (YYYY-MM-DD)

positionStartDateMinstring

Minimum date for when a contact began current employment (YYYY-MM-DD)

primaryIndustriesOnlyboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. When set to true, any result returned must have one of the specified industries as a primary industry

recentFundingRoundTypesarray

Filters for companies whose most recent funding round matches one of the given types. Accepts an array of values from the endpoint: /lookup/funding-round-types. This is a different filter mode than allFundingRoundTypes (which matches any round in the company's history), so only one of the two should be supplied per request.

requiredFieldsstring

**Deprecated:** use `requiredFieldsList` instead. A comma-separated list of required fields for each record returned. Indicates that a contact must have all of the specified fields to be included in search results, NOT that the fields will be returned in the results. Can include email (business email), phone (direct or company phone), directPhone (contact's direct phone), personalEmail, and mobilePhone. Example with all possible valid values: "email,phone,personalEmail,mobilePhone,directPhone".

requiredFieldsListarray

A list of required fields for each record returned. Indicates that a contact must have all of the specified fields to be included in search results, NOT that the fields will be returned in the results. Can include email (business email), phone (direct or company phone), directPhone (contact's direct phone), personalEmail, and mobilePhone.

revenuestring

**Deprecated:** use `revenueMin`/`revenueMax` instead. Annual revenue range in U.S. dollars. Accepts a comma-separated list of values. Valid values: under500K, 500Kto1M, 1Mto5M, 5Mto10M, 10Mto25M, 25Mto50M, 50Mto100M, 100MMto250M, 250Mto500M, 500Mto1G, 1Gto5G, 5GPlus Example: "1Mto5M,10Mto25M" will return companies with annual revenue in either of those ranges.

revenueMaxinteger

Maximum annual revenue for a company in U.S. dollars (expressed in thousands)

revenueMininteger

Minimum annual revenue for a company in U.S. dollars (expressed in thousands)

schoolstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. School name

sicCodesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Standard Industrial Classification codes. Accepts a comma-separated list of values from the lookup tool with fieldName: "sic-codes"

sortstring

Sort field for results. Use minus sign prefix for descending order.

Options:-companyName-contactAccuracyScore-hierarchy-lastMentioned-lastName-relevance-sourceCountcompanyNamecontactAccuracyScorehierarchylastMentionedlastNamerelevancesourceCount
statestring

Accepts a comma-separated list of states or provinces from the U.S. and Canada. Use ZoomInfo lookup tool with fieldName: "states" to get acceptable values. Combined with country, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

streetstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Street address portion of the company's location

subUnitTypesstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Company sub types (e.g., division, subsidiary). Use with parentId or ultimateParentId

supplementalEmailarray

**Deprecated:** retained for backward compatibility only; no longer actively supported. Supplemental email addresses for the contact

techAttributeTagIdListarray

Technology Product Tags. Use values from the id field returned from ZoomInfo lookup tool with fieldName: "tech-products". First lookup tech-vendors with fuzzyMatch to find vendor, then lookup tech-products with vendor parameter.

techAttributeTagListstring

**Deprecated:** use `techAttributeTagIdList` instead. Technology Product Tags. Use values returned from ZoomInfo lookup tool with fieldName: "tech-products". First lookup tech-vendors with fuzzyMatch to find vendor, then lookup tech-products with vendor parameter. Can include a comma-separated list of product IDs.

techSkillsarray

**Deprecated:** retained for backward compatibility only; no longer actively supported. List of technology skill IDs for a contact. Should only contain string numbers

twoYearEmployeeGrowthRateMaxstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum two year employee growth rate for a company

twoYearEmployeeGrowthRateMinstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum two year employee growth rate for a company

ultimateParentIdstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. ZoomInfo Company ID for ultimate parent company. Id must be an integer and cannot be zero.

underManagementboolean

**Deprecated:** retained for backward compatibility only; no longer actively supported. Returns whether or not record is under management if set to true

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

validDateAfterstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. The date after which the contact's profile was last validated (YYYY-MM-DD)

webReferencesarray

**Deprecated:** retained for backward compatibility only; no longer actively supported. List of Web References for a contact. Should only contain english letters and numbers

yearsOfExperiencestring

**Deprecated:** use `yearsOfExperienceList` instead. Total years of experience. Accepts a comma-separated list

yearsOfExperienceListarray

Total years of experience

zipCodestring

Zip code or postal code. Unlike the other location fields (state, country, continent, metroRegion), which combine with each other using OR semantics (union), zipCode is intersected (AND semantics) with the combined result of all other supplied location fields, rather than being OR'd in as an additional branch of the union.

zipCodeRadiusMilesstring

Geographical radius (in miles) from the zipCode provided. Supported values: 10, 25, 50, 100, 250. The parameter zipCodeRadiusMiles requires that zipCode is non-null and valid.

Options:102550100250
zoominfoContactsMaxstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Maximum number of ZoomInfo contacts associated with company

zoominfoContactsMinstring

**Deprecated:** retained for backward compatibility only; no longer actively supported. Minimum number of ZoomInfo contacts associated with company

Search Intent Signals

search_intent
Full Description

Search for Intent Signals across ZoomInfo's comprehensive database. Intent Signals indicate recent content consumption and buying interest by companies for specific topics.

Required: Every request must include at least 1 and up to 50 intent topics.

Key Terminology: • Topic

  • A business subject or technology area mapped to a curated collection of keywords and search terms. When companies research content containing these keywords, it generates intent signals that indicate their buying interest

• Signal Score

  • Indicates the level of a company's interest in a topic (60-100) based on how recent content consumption compares to an historical baseline

• Audience Strength

  • Indicates the size of the group at the company that is conducting the research (A=largest audience, E=smallest)

🔍 **Recommended Workflow

  • Using Lookup for Accurate Results:**

For intent searches with specific topics, you should:

1. Call lookup with fields: [{ fieldName: "intent-topics" }] to get standardized topic values 2. Call search_intent with exact topic names from lookup results

Example: "Find companies interested in Cloud Applications and Java":

1. lookup(fields: [{ fieldName: "intent-topics", fuzzyMatch: "cloud" }, { fieldName: "intent-topics", fuzzyMatch: "java" }])
   → Returns topics: ["Cloud Applications", "Java", ...]
2. search_intent(topics: ["Cloud Applications", "Java"], signalScoreMin: 70, audienceStrengthMin: "B")

Example: "Companies showing high intent for Mobile Apps in the last 30 days":

1. lookup(fields: [{ fieldName: "intent-topics", fuzzyMatch: "mobile" }])
   → Returns topics: ["Mobile Apps", "Mobile / Wireless", ...]
2. search_intent(topics: ["Mobile Apps"], signalScoreMin: 80, signalStartDate: "2024-01-01", signalEndDate: "2024-01-31")

Note: Using exact topic names returned by lookup ensures accurate search results. The lookup response includes both a topics array (topic names) and topicDetails array (with additional metadata like category, department, description). Use the topic names from either array in your search_intent request.

Use Search Intent to find Intent Signals across all ZoomInfo companies. To find Intent Signals for a specific company, use the Enrich Intent endpoint.

CREDITS: Free to use

Parameters (0 required, 52 optional)
Optional
addressstring

Full company address

audienceStrengthMaxstring

Maximum audience strength. Values: A, B, C, D, E — A indicates the largest audience and the highest maximum strength. Use with audienceStrengthMin to set a range where audienceStrengthMax must be closer to A than audienceStrengthMin. For example, audienceStrengthMax: B and audienceStrengthMin: D will return results with audience strength of B, C, or D but not E.

Options:ABCDE
audienceStrengthMinstring

Minimum audience strength. Values: A, B, C, D, E — E indicates the smallest audience and the lowest minimum strength. Use with audienceStrengthMax to set a range.

Options:ABCDE
businessModelarray

Business model: B2C, B2B, B2G. Default: All

companyDescriptionstring

Filter by company description keywords (space-separated)

companyRankingstring

Company ranking list IDs (e.g., Fortune 500). Comma-separated

companyStructureIncludedSubUnitTypesstring

Hierarchical structure filter. Values: UNSPECIFIED, LOCATION, DIVISION, ACQUISITION, SUBSIDIARY, FORMER_NEW_NAME. Comma-separated

companyTickerarray

Company stock ticker symbols

companyTypestring

Company type (private, public, etc.). Comma-separated

continentstring

Continent name. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "continents" to get acceptable values. Combined with state, country, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

countrystring

Accepts a comma-separated list of countries. Use ZoomInfo lookup tool with fieldName: "countries" to get acceptable values. Combined with state, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

employeeCountstring

Employee count range. Accepts a comma-separated list of values. Alternatively, for more granular ranges, you can use the employeeRangeMin and employeeRangeMax parameters. Valid values are: 1to4, 5to9, 10to19, 20to49, 50to99, 100to249, 250to499, 500to999, 1000to4999, 5000to9999, 10000plus Example: "10to19,50to99" will return companies with employee counts in either of those ranges.

employeeRangeMaxstring

Maximum employee count. Accepts a single positive integer. Use with employeeRangeMin for granular ranges.

employeeRangeMinstring

Minimum employee count. Accepts a single positive integer. Use with employeeRangeMax for granular ranges.

excludedRegionsstring

U.S. and Canada states or metro areas to exclude. Comma-separated.

findRecommendedContactsboolean

Whether to include recommended contacts in results. Can include a large amount of contact data and lead to timeouts, so use with caution. Default: false. Set to true to include

fundingAmountMaxinteger

Maximum funding in thousands. Use with fundingAmountMin.

fundingAmountMininteger

Minimum funding in thousands. Use with fundingAmountMax.

fundingEndDatestring

End of funding date range (YYYY-MM-DD).

fundingStartDatestring

Start of funding date range (YYYY-MM-DD).

hashTagStringstring

ZoomInfo hashtags. Comma-separated.

industryCodesstring

Industry classifications. Comma-separated. Use Lookup industries for valid values.

industryKeywordsstring

Industry keywords. Supports AND / OR operators (e.g., software AND security).

locationSearchTypestring

Whether the location filter should apply to the Person or the Company's Headquarters. Location scope: PersonOrHQ, PersonAndHQ, Person, HQ, PersonThenHQ). When locationSearchType is passed in, a value must be provided for at least one of the following parameters: state, country, continent, metroRegion, zipCode, address.

metroRegionstring

Company metro area. Accepts a comma-separated list of U.S. and Canada metro areas. Use ZoomInfo lookup tool with fieldName: "metro-regions" to get acceptable values. Combined with state, country, or continent using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

naicsCodesstring

North American Industry Classification System codes. Accepts a comma-separated list from the lookup tool with fieldName: "naics-codes"

oneYearEmployeeGrowthRateMaxstring

Maximum 1-year employee growth rate. Use with oneYearEmployeeGrowthRateMin.

oneYearEmployeeGrowthRateMinstring

Minimum 1-year employee growth rate. Use with oneYearEmployeeGrowthRateMax.

pageinteger

Page number for pagination

pageSizeinteger

Number of results per page. Pagination caps at 10,000 total records.

primaryIndustriesOnlyboolean

When true, results must have one of the specified industries as primary. Default: false.

revenuestring

Annual revenue range. Comma-separated.

revenueMaxinteger

Maximum revenue in thousands. Use with revenueMin.

revenueMininteger

Minimum revenue in thousands (e.g., 1 = $1,000). Use with revenueMax.

sicCodesstring

Standard Industrial Classification codes. Accepts a comma-separated list of values from the lookup tool with fieldName: "sic-codes"

signalEndDatestring

End date for signal activity (YYYY-MM-DD)

signalScoreMaxinteger

Maximum signal score. Valid range: 60-100. Use with signalScoreMin to set a range.

signalScoreMininteger

Minimum signal score. Valid range: 60-100. Use with signalScoreMax to set a range.

signalStartDatestring

Start date for signal activity (YYYY-MM-DD)

sortstring

Sort field for results. Use minus sign prefix for descending order.

Options:-audienceStrength-category-companyName-signalDate-signalScore-topicaudienceStrengthcategorycompanyNamesignalDatesignalScoretopic
statestring

Accepts a comma-separated list of states or provinces from the U.S. and Canada. Use ZoomInfo lookup tool with fieldName: "states" to get acceptable values. Combined with country, continent, or metroRegion using OR semantics (union). If zipCode is also supplied, this field is combined with zipCode using AND semantics (intersection) instead.

streetstring

Street address

subUnitTypesstring

Company sub-types (e.g., division, subsidiary). Use with parentId or ultimateParentId.

techAttributeTagListstring

Technology product tags. Comma-separated. Use Lookup tech-products for valid values

topicsarray

Intent topic names. Accepts an Array of up to 50 topic name Strings. Use the lookup tool with fieldName: 'intent-topics' to get valid topic names. If empty or not provided, all configured topics (up to 50) will be used.

twoYearEmployeeGrowthRateMaxstring

Maximum 2-year employee growth rate. Use with twoYearEmployeeGrowthRateMin.

twoYearEmployeeGrowthRateMinstring

Minimum 2-year employee growth rate. Use with twoYearEmployeeGrowthRateMax.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zipCodestring

Zip code or postal code. Unlike the other location fields (state, country, continent, metroRegion), which combine with each other using OR semantics (union), zipCode is intersected (AND semantics) with the combined result of all other supplied location fields, rather than being OR'd in as an additional branch of the union.

zipCodeRadiusMilesstring

Radius in miles from zipCode. Supported values: 10, 25, 50, 100, 250. The parameter zipCodeRadiusMiles requires that zipCode is non-null and valid.

zoominfoContactsMaxstring

Maximum number of ZoomInfo contacts at the company

zoominfoContactsMinstring

Minimum number of ZoomInfo contacts at the company

Search Scoops

search_scoops
Full Description

Search for Scoops across ZoomInfo's comprehensive database. Scoops are real-time business intelligence signals that provide timely insights into significant events and changes occurring at companies.

SCOOP FILTERS: • scoopIds

  • ZoomInfo unique identifiers for Scoops

• scoopTypes

  • Retrieve scoops based on type (e.g. Earnings, Award, and Partnership).

• scoopTopics

  • Retrieve scoops based on topic (e.g. integration, consolidation and compliance). Accepts a list of IDs from the lookup tool

• department

  • Retrieve scoops based on department (IT, finance, HR and so on).

• description

  • Search for scoops based on description. Accepts a space-separated list of individual words

• publishedStartDate

  • Starting date to search for scoops based on publication date (YYYY-MM-DD format)

• publishedEndDate

  • Ending date to search for scoops based on publication date (YYYY-MM-DD format)

• updatedSinceCreation

  • Setting true will only return scoops that have been updated since publishedStartDate

COMPANY FILTERS: • companyTicker, companyDescription, companyTypes

  • Identify or describe specific companies

• industryCodes, metroRegions, employeeCount, revenue

  • Filter by company attributes

• techAttributeTagList

  • Filter by technology stack (use Lookup tech-products for valid values)

CONTACT FILTERS: • jobTitle, managementLevel, department, jobFunction

  • Filter by contact role

• firstName, lastName, emailAddress

  • Filter by specific contact

SORT OPTIONS: • scoopId, originalPublishedDate (default: -originalPublishedDate), description, link, linkText • Prefix with '-' for descending order

USE CASES: • Find companies with recent leadership changes or expansions • Identify companies that recently received funding or made acquisitions • Track industry-specific business events for timely outreach • Discover companies showing signals of buying intent through business events

RECOMMENDED WORKFLOW: 1. Use Lookup with fieldName: "scoop-topics" to get valid filter IDs 2. Call search_scoops with the desired filters 3. Use Enrich Scoops for detailed scoop data on a specific company

CREDIT USAGE: This endpoint does not consume any Credits. Each Scoop returned counts towards the customer's Record Limit and a successful response counts towards the Request Limit.

Parameters (0 required, 74 optional)
Optional
addressstring

Full company address.

boardMemberstring

Exclude or include board members from search results. Default behavior is to exclude board members.

Options:includeexcludeonly
businessModelarray

Search using Business Model for a company. Default is All.

certifiedstring

Denotes if ZoomInfo's research and data team has confirmed activity within the past 12 months.

Options:10
companyDescriptionstring

Search for companies based on description. Accepts a space-separated list of individual words.

companyPastOrPresentstring

Defaults to only include the present company for a contact.

Options:presentpastpastAndPresent
companyRankingsarray

Company rankings.

companyStructureIncludedSubUnitTypesarray

Company hierarchical structure sub-unit types to include in results.

companyTickerarray

Company stock ticker symbols.

companyTypesarray

Company types.

contactAccuracyScoreMaxinteger

Maximum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99.

contactAccuracyScoreMininteger

Minimum accuracy score for search results. This score indicates the likelihood that a contact is reachable and still employed by the company listed. Minimum score is 70 and maximum is 99.

continentstring

Continent of the primary address of the associated company.

countrystring

Country of the primary address of the associated company.

degreestring

Searches by contact's education.

departmentarray

Retrieve scoops based on department.

descriptionstring

Search for scoops based on description. Accepts a space-separated list of individual words.

emailAddressstring

Email address for the contact in example@example.com format.

employeeCountarray

Employee count ranges. Alternatively, for more granular ranges, you can use the employeeRangeMin and employeeRangeMax parameters. Valid values are: 1to4, 5to9, 10to19, 20to49, 50to99, 100to249, 250to499, 500to999, 1000to4999, 5000to9999, 10000plus Example: ["10to19","50to99"] will return companies with employee counts in either of those ranges.

employeeRangeMaxinteger

Maximum employee count. Use with employeeRangeMin to set a range.

employeeRangeMininteger

Minimum employee count. Use with employeeRangeMax to set a range.

excludedRegionsarray

U.S. and Canada states and metro areas to exclude from results.

excludeJobTitlesarray

Job titles to exclude from search results.

excludeManagementLevelsarray

Management levels to exclude from search results.

excludePartialProfilesboolean

Defaults to false. To include partial profiles in your search results, set this to true.

executivesOnlyboolean

Defaults to false. Set this to true to include only Executives in search results.

firstNamestring

Contact first name.

fullNamestring

Contact full name.

fundingAmountMaxinteger

Maximum funding amount in thousands. Use with fundingAmountMin to set a range.

fundingAmountMininteger

Minimum funding amount in thousands. Use with fundingAmountMax to set a range.

fundingEndDatestring

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

fundingStartDatestring

Start date of the funding in YYYY-MM-DD format.

hasBeenNotifiedstring

Defaults to include. Filter contacts based on whether they have been notified of inclusion in ZoomInfo's database.

Options:includeexcludeonly
hashedEmailstring

Hashed email value for the contact. Supported hash algorithms are: MD5, SHA1, SHA256 and SHA512.

hashTagStringsarray

Hashtag-based search criteria for filtering companies. Use ZoomInfo lookup tool with fieldName: "hashtags" to get acceptable values.

industryCodesarray

Top-level industry codes. Use ZoomInfo lookup tool with fieldName 'industries' to get acceptable values.

industryKeywordsstring

Industry keywords. Can include either 'AND' or 'OR' operators.

jobFunctionarray

Contact job function at their current place of employment.

jobTitlearray

Contact job title at current place of employment.

lastNamestring

Contact last name.

lastUpdatedInMonthsinteger

Number of months within which the contact's profile was last updated.

locationSearchTypestring

Whether the location filter should apply to the Person or the Company's Headquarters. When locationSearchType is passed in, a value must be provided for at least one of the following parameters: state, country, continent, metroRegion, zipCode, address.

Options:PersonOrHQPersonAndHQPersonHQPersonThenHQ
managementLevelsarray

Contact management levels at current place of employment

metroRegionsarray

Company metro areas from the U.S. and Canada. Use ZoomInfo lookup tool with fieldName: "metro-regions" to get acceptable values.

middleInitialstring

Contact middle initial.

oneYearEmployeeGrowthRateMaxnumber

Maximum one-year employee growth rate. Use with oneYearEmployeeGrowthRateMin to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

oneYearEmployeeGrowthRateMinnumber

Minimum one-year employee growth rate. Use with oneYearEmployeeGrowthRateMax to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

pageinteger

Page number for pagination

pageSizeinteger

Number of results per page. Pagination caps at 10,000 total records.

personIdsarray

ZoomInfo unique identifiers for contacts.

primaryIndustriesOnlyboolean

Default is false. When set to true, any result returned must have one of the specified industries as a primary industry.

publishedEndDatestring

Ending date to search for scoops based on publication date. Form a range using publishedStartDate. Uses YYYY-MM-DD format.

publishedStartDatestring

Starting date to search for scoops based on publication date. Form a range using publishedEndDate or omit publishedEndDate to search to the current date. Uses YYYY-MM-DD format.

requiredFieldsarray

Fields that must be present for a record to return.

revenuestring

Annual revenue range.

Options:under500k500kto1m1mto5m5mto10m10mto25m25mto50m50mto100m100mmto250m250mto500m500mto1g1gto5g5gplus
revenueMaxinteger

Maximum annual revenue in thousands. Use with revenueMin to set a range.

revenueMininteger

Minimum annual revenue in thousands. Use with revenueMax to set a range.

schoolstring

School name.

scoopIdsarray

ZoomInfo unique identifiers for Scoops.

scoopTopicsarray

Retrieve scoops based on topic (e.g. integration, consolidation and compliance). Accepts a list of IDs from the lookup tool.

scoopTypesarray

Retrieve scoops based on type.

sortstring

Sort field for results. Use minus sign prefix for descending order. Default is -originalPublishedDate.

Options:scoopId-scoopIdoriginalPublishedDate-originalPublishedDatedescription-descriptionlink-linklinkText-linkText
statestring

State or province. Accepts a comma-separated list of values. Use ZoomInfo lookup tool with fieldName: "states" to get acceptable values.

streetstring

Street address portion of the company's location.

subUnitTypesarray

Company sub-types (e.g., division, subsidiary). Use in conjunction with parentId or ultimateParentId.

techAttributeTagListarray

Technology product tags. Use ZoomInfo lookup tool with fieldName 'tech-products' to get acceptable values.

twoYearEmployeeGrowthRateMaxnumber

Maximum two-year employee growth rate. Use with twoYearEmployeeGrowthRateMin to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

twoYearEmployeeGrowthRateMinnumber

Minimum two-year employee growth rate. Use with twoYearEmployeeGrowthRateMax to set a range. Accepts a number with up to 1 decimal place. Example: a value of 25.1 means 25.1% growth.

updatedSinceCreationboolean

Default is false. Setting true will only return scoops that have been updated since publishedStartDate.

userIntentstring

Free-form context provided by the calling LLM agent describing the request being made (e.g., the original user query or a summary of the use case). Used by ZoomInfo for audit and personalization.

zipCodestring

Zip code or postal code of the company's address.

zipCodeRadiusMilesstring

Used in conjunction with zipCode, designates a geographical radius (in miles) from the zipCode provided. The parameter zipCodeRadiusMiles requires that zipCode is non-null and valid.

Options:102550100250
zoominfoContactsMaxinteger

Maximum number of ZoomInfo contacts associated with company.

zoominfoContactsMininteger

Minimum number of ZoomInfo contacts associated with company.

Submit Feedback

submit_feedback
Full Description

Use this tool to submit feedback on ZoomInfo MCPs or other feedback for ZoomInfo. Required:

  • Provide feedback content.
  • Provide a category for the feedback. Select the most appropriate value: DATA_QUALITY, FEATURE_REQUEST, ACCESS_ENTITLEMENT_ISSUE, or OTHER.

CREDITS: Free to use

Parameters (2 required)
Required
categorystring

Allowed categories for feedback submission. - DATA_QUALITY: Feedback related to the quality of data returned by ZoomInfo mcp tools. - FEATURE_REQUEST: Feedback requesting a new feature or enhancement. - ACCESS_ENTITLEMENT_ISSUE: Feedback about access or entitlement issues. - OTHER: Feedback that does not fit the other categories.

Options:DATA_QUALITYFEATURE_REQUESTACCESS_ENTITLEMENT_ISSUEOTHER
feedbackstring

Feedback content.

Update GTM Context

update_gtm_context
Full Description

Update your organization's GTM configuration. Can synthesize unstructured content into structured records, or make direct changes to existing configuration.

WHAT IT MANAGES: • Company Overview (name, elevator pitch, description, strategic priorities, custom fields) • Offerings / Products (value props, pain points, proof points, custom fields) • Buyer Personas (roles, objectives, pain points, priorities, custom fields) • Ideal Customer Profiles / ICPs (segments, firmographics, technographics, custom fields) • Competitors (products, strengths, weaknesses, win/loss reasons, custom fields)

ENTITY LIFECYCLE - all entities (except Company Overview) support these state transitions: • active to archived: "archive this item" - soft-remove, hidden but recoverable • active to deleted: "delete this item" - permanent removal, irreversible • archived to active: "unarchive this item" - restore a previously archived item to active • archived to deleted: "delete this archived item" - permanently remove an archived item

ARCHIVE vs DELETE (IMPORTANT): Archive is REVERSIBLE (the item can be restored later). Delete is PERMANENT and IRREVERSIBLE. When the user says "remove" or "get rid of" without explicitly saying "permanently delete" or "destroy", ALWAYS use archive, not delete. Only use delete when the user explicitly says "delete", "permanently delete", "permanently remove", or "destroy".

UNARCHIVE / RESTORE: When the user says "unarchive", "restore", "reactivate", "bring back", or "make active again", use the unarchive action to move an archived entity back to active status.

ACTIONS SUMMARY: The agent can Create, Read, Update, Archive, Unarchive, and Delete configuration (Offerings, Buyer Personas, Ideal Customer Profiles, Competitors). The Company Overview settings can only be created and updated (no archive or delete). Ask clarifying questions for destructive operations. If the user asks to delete many objects, make sure this is wanted and clarify requests to delete or archive objects. Ask clarifying questions for confusing requests. If the user creates when the object already exists, then ask for a confirmation to update the object.

CUSTOM FIELDS: The agent can create and populate custom fields on any object type. When you provide information that doesn't fit standard fields, the agent will create appropriate custom fields to preserve that context. For example: "integration timeline", "decision maker", "budget cycle", or domain-specific attributes unique to your sales process.

MULTI-OBJECT OPERATIONS: A single call can affect multiple object types. The agent deduplicates against existing configuration and enriches existing records where appropriate.

FOR BEST RESULTS: The query frames your intent, while sourceMaterial provides substance to analyze. When sourceMaterial is provided, richer content produces higher-quality records. When omitted, the agent operates on existing configuration directly (archive, unarchive, rename, simple updates).

CONTEXT LIMITS: sourceMaterial should not exceed ~2,000 words per call. For larger documents, break into multiple calls with scoped queries.

CREDITS: Each query consumes ZoomInfo AI credits. Credit consumption scales with the amount of content analyzed and the complexity of operations performed.

ACCESS: User must be an admin in the ZoomInfo system.

Parameters (1 required, 1 optional)
Required
querystring

Natural language instruction framing your intent and scope. State the action (create / update / archive / unarchive / delete), the entity type, and any relevant details (entity name, field values). Examples: • "Create a new buyer persona for CFOs in healthcare" • "Update Competitor X's description to mention their new product launch" • "Archive the Startup ICP" • "Unarchive the Enterprise CTO persona" • "Restore the old Startup ICP" • "Permanently delete the archived SMB competitor"

Optional
sourceMaterialstring

Raw content to analyze and synthesize into structured records: strategy notes, product brief, competitive intel, brain dump, transcript. Limit to ~2,000 words. For larger documents, break into multiple calls with scoped queries. When omitted, agent operates on existing configuration directly.