# ZoomInfo MCP connector

The ZoomInfo connector lets Claude, ChatGPT, Cursor and Microsoft Copilot search and enrich ZoomInfo contacts, companies, intent signals, scoops and news, with each person inside their own ZoomInfo access and every lookup logged.

Source: https://elaichi.ai/connectors/zoominfo/

## Facts

| | |
| --- | --- |
| Application | ZoomInfo |
| Category | Sales Intelligence |
| AI tools | 113 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once ZoomInfo is connected

- Find VP-level marketing contacts at fintech companies in Texas
- Which of my target accounts show intent for data security?
- Summarize this week's scoops and news for Acme Corp

## Connect ZoomInfo in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ZoomInfo.
2. Optionally set Share with, then press Connect.
3. Supply your own ZoomInfo app, then approve. ZoomInfo needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ZoomInfo tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ZoomInfo MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## ZoomInfo MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## ZoomInfo MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## ZoomInfo MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## ZoomInfo MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect ZoomInfo to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a ZoomInfo tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ZoomInfo through Elaichi

### Research an account before the first call

Sales. Ask for a company's size, revenue, technologies and recent scoops from ZoomInfo, then the right contacts to reach, and get it in one answer instead of six tabs.

### Build a prospect list from plain words

Sales development. Describe the companies and job titles you want and get a list of ZoomInfo contacts with direct lines and emails, ready to work.

### Spot accounts showing buying intent this week

Marketing. Pull ZoomInfo intent signals for your target topics and see which accounts are warming up before the campaign goes out.

### Fill the gaps in a messy record

Revenue operations. Hand over a company name or an email address and get the ZoomInfo enrichment back, with the fields the CRM is missing and how much of your usage limit is left.

### Catch a leadership change at a customer

Customer success. Check ZoomInfo scoops and news for a renewal account to find new executives, funding rounds or layoffs before the next check-in.

### Map the org chart of a target

Partnerships. Ask for a ZoomInfo org chart and corporate hierarchy to see who reports to whom and which subsidiaries belong to the parent company.

## Elaichi vs Zapier MCP vs Composio for ZoomInfo

All three can connect ZoomInfo to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over ZoomInfo tools | Allow or restrict single ZoomInfo tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per ZoomInfo call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect ZoomInfo to Claude?

Connect ZoomInfo in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. ZoomInfo connects over OAuth, but ZoomInfo asks you to register an OAuth application inside your own ZoomInfo admin settings, so whoever sets it up brings that client ID and secret to Elaichi once. After that one-time step nobody else ever generates or handles a client ID or secret, and each person simply signs in to ZoomInfo as themselves.

### Does ZoomInfo work with ChatGPT and Cursor as well as Claude?

Yes. Once ZoomInfo is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect ZoomInfo once and every client picks it up.

### What can an AI agent actually do with my ZoomInfo data?

It can search ZoomInfo for companies and contacts that match a description, enrich a record you already have with ZoomInfo's fields, and pull intent signals, scoops, news, technologies, org charts and corporate hierarchies for an account. It can also check your ZoomInfo usage limits and start or review ZoomInfo agent runs. Short, concrete asks such as "find marketing VPs at fintech companies in Texas" work better than long paragraphs.

### Does connecting ZoomInfo give the AI my whole ZoomInfo license?

No. Every call runs as the person who signed in to ZoomInfo, so the AI sees only the contacts, companies, intent topics and credits that person's ZoomInfo seat already allows. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what ZoomInfo itself grants.

### Can my team share one ZoomInfo connection?

Yes. One person connects ZoomInfo in Elaichi and shares the connection with a team, and nobody else ever touches the ZoomInfo client ID or secret. Each teammate still signs in as themselves, so the audit log shows exactly who searched for which contact or enriched which company.

### Can I stop an agent from running ZoomInfo enrichments or agent runs that use credits?

Yes. Restrictions in Elaichi work per action, set on a role or on one person, so you can let someone search ZoomInfo but restrict enriching contacts or starting ZoomInfo agent runs. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a ZoomInfo connection when someone leaves?

Offboarding that person in Elaichi ends their ZoomInfo access through every client at once. A ZoomInfo connection they shared keeps working for everyone else on the team. If you ever want ZoomInfo gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

### Does the ZoomInfo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. ZoomInfo is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for ZoomInfo?

Yes. Both let Claude, ChatGPT or Cursor use ZoomInfo. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ZoomInfo call.

### How is Elaichi different from Composio for ZoomInfo?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ZoomInfo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 113 ZoomInfo tools

Every tool below is callable through https://api.elaichi.ai/mcp once ZoomInfo is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all ZoomInfo contacts** (List). Search ZoomInfo contacts by criteria such as companyName, firstName, lastName or personId, sent in the JSON request body (data). Returns id, type and attributes (company, names, jobTitle, contactAccuracyScore, hasEmail-style hints); no emails or phone numbers. Up to 100 per page; paging stops at page 100.
- **ZoomInfo contacts enrich** (Action). Enrich up to 25 ZoomInfo contacts per request using matchPersonInput (personId or name/company details) and outputFields. Returns: id, type, attributes, meta. NO_MATCH results incur no credit; every enriched record counts against the Record Limit. Required: data.
- **List all ZoomInfo companies** (List). Search ZoomInfo companies by criteria such as companyName, metroRegion or industryCodes, sent in the JSON request body (data). Returns id, type and attributes with basic info only; use companies.enrich for full details. Up to 100 per page; paging stops at page 100.
- **ZoomInfo companies enrich** (Action). Enrich up to 25 ZoomInfo company records per call, matching on companyId, companyWebsite, or other company attributes (ipAddress must be the sole input for a record). Returns per record: id, type, meta.matchStatus, and attributes carrying the requested outputFields such as name, website, revenue, and socialMediaUrls. Required: data.
- **List all ZoomInfo lookup values** (List). List the allowed values of one ZoomInfo lookup field, such as countries, industries or management levels. Returns: id, type, attributes. Required: field_name. Omitting field_name sends an invalid path and ZoomInfo returns an error.
- **List all ZoomInfo search fields** (List). List the ZoomInfo search fields available for an entity, filtered by entity and field type, with whether the account has access to each. Returns: id, type, attributes. Required: filter (filter[entity], filter[fieldType]).
- **List all ZoomInfo enrich fields** (List). List ZoomInfo enrich input or output fields for an entity, with whether the account has access to each. Returns: id, type, attributes. Required: filter (filter[entity], filter[fieldType]).
- **List all ZoomInfo usage limits** (List). Get the current user's ZoomInfo API usage and limits. Returns: id, type, attributes. Takes no parameters.
- **List all ZoomInfo intents** (List). Search ZoomInfo Intent Signals across all companies that match the given search criteria. Returns: id, type, attributes. Required: data containing attributes.topics (1–50 intent topics per request). Needs api:data:intent enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). Intent SKU required. No credits consumed; each Intent Signal returned counts as a Record and a successful response counts as a Request credit.
- **ZoomInfo intents enrich** (Action). Fetch Intent Signals for a single company in ZoomInfo, enriching it with buyer intent data. Returns intent records with type, id, and attributes including topic, signalScore, audienceStrength, signalDate, and recommendedContacts. Required: data. In data.attributes send topics (1-50) and at least one company identifier (companyId, companyName or companyWebsite). Needs api:data:intent enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). Intent SKU required. Charges a single credit for the enriched company (no credit if it is already under management); each Intent Signal returned counts as a Record, and each successful response counts as a Request. Results are paged (page.number, page.size); the connector does not auto-paginate enrich calls and returns only the data array. Request the next page.number until a page returns fewer than page.size records (REST /proxy callers can also add truto_response_format=raw to read meta.page.total, the total page count).
- **List all ZoomInfo news** (List). Search ZoomInfo news articles by criteria such as categories and a publish-date range. Returns: id, type, attributes. At least one search criterion must be set. Required: data (with type and search attributes). Needs api:data:news enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). No credits consumed; each news article returned counts towards the Record Limit.
- **ZoomInfo news enrich** (Action). Enrich a specified ZoomInfo company with relevant news articles. Returns news article records with id, type, and attributes including title, url, pageDate, and categories. Required: data. In data.attributes send companyId (ZoomInfo's text also names companyName and companyWebsite, but its request schema declares only companyId). Needs api:data:news enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). A credit is counted for the enriched company (not per article); each article returned counts towards the Record Limit. Results are paged (page.number, page.size); the connector does not auto-paginate enrich calls and returns only the data array. Request the next page.number until a page returns fewer than page.size records (REST /proxy callers can also add truto_response_format=raw to read meta.page.total, the total page count).
- **List all ZoomInfo scoops** (List). Search ZoomInfo Scoops across all companies by criteria like scoopType, publishedStartDate, and updatedSinceCreation. Returns Scoop records (type, id, attributes) with company, description, originalPublishedDate, publishedDate, types, topics. Required: data (search criteria go in data.attributes). Sort defaults to -originalPublishedDate. Needs api:data:scoops enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). No credits consumed; each Scoop returned counts towards the Record Limit.
- **ZoomInfo scoops enrich** (Action). Enrich a ZoomInfo company with relevant Scoops (news items). Returns Scoop records with type, id, and attributes including company, description, and published dates. Required: data. In data.attributes send one company identifier (companyId, companyName or companyWebsite). Needs api:data:scoops enabled on the ZoomInfo OAuth app and in the package, else 403 (ZI0002/ZI0003). A credit is counted for the enriched company (not per Scoop); each Scoop returned counts towards the Record Limit. Results are paged (page.number, page.size); the connector does not auto-paginate enrich calls and returns only the data array. Request the next page.number until a page returns fewer than page.size records (REST /proxy callers can also add truto_response_format=raw to read meta.page.total, the total page count).
- **ZoomInfo corporate hierarchies enrich** (Action). Enrich the corporate hierarchy of up to 25 ZoomInfo companies per request; the data envelope carries matchCompanyInput and outputFields (type CorporateHierarchyEnrich). Returns records with id, type, attributes (companyId, familyTree), meta (matchStatus, input); NoMatch when nothing matches. Required: data. Needs OAuth scope api:data:company. Each record returned charges a credit unless already under management; NoMatch or error responses are not charged.
- **ZoomInfo org charts enrich** (Action). Enrich a ZoomInfo company's org chart and return its contacts organized by department and seniority tier. Returns the org chart records including id, title, department, orgChartTier, and companyName. Required: data. In data.attributes send companyId and department (ZoomInfo requires at least one department). Needs OAuth scope api:data:contact. A credit is counted for the enriched company, when applicable. Counts one Record per successful request, regardless of how many contacts are returned. Results are paged (page.number, page.size); the connector does not auto-paginate enrich calls and returns only the data array. Request the next page.number until a page returns fewer than page.size records (REST /proxy callers can also add truto_response_format=raw to read meta.page.total, the total page count).
- **ZoomInfo company technologies enrich** (Action). Enrich Technologies for a matched ZoomInfo company, returning the list of technologies that company uses, identified from company websites, job postings, and data partnerships. Returns: id, type, attributes. Required: data (data.type and data.attributes). companyId in data.attributes is the only input, one company per request. Needs OAuth scope api:data:company. Charges a single credit for the enriched company.
- **ZoomInfo company hashtags enrich** (Action). Enrich a ZoomInfo company with its hashtags: predefined categorical labels that classify companies for filtering and segmentation. Returns matching hashtag records with id, type, and attributes (label, group, description, parentCategory, priority). Required: data (data.type and data.attributes). companyId in data.attributes is the only input, one company per request. Needs OAuth scope api:data:company. Charges a single credit for the enriched company (no credit if it is already under management).
- **List all ZoomInfo agents** (List). List Agents. Lists all agents available to your tenant, including ZoomInfo managed agents and your tenant's published Agent Teams. Before running an agent, use Get Agent Details to review its required inputs and supported capabilities. Per Credit Usage and Limits, this endpoint does not consume credits.
- **Get single ZoomInfo agent by ID** (Get). Get Agent Details. Retrieves the full details for a specific agent, including the inputs required to run it. Call this endpoint before starting a run. The expected input is defined in `inputSchema`, which describes the message parts the agent accepts, such as `text` or structured `data`, and whether each part is required. For structured input, the `schema` defines the payload that must be provided in the corresponding `data` part of Start Agent Run. `inputSchema` is returned only by this endpoint and is not included in List Agents. It is omitted when the agent does not define an input contract. Required: id.
- **Create a ZoomInfo agent run** (Create). Start Agent Run. Starts a new run for the specified agent. By default, agent runs are asynchronous. The request returns the in-progress run, including its run id in `data.id`, while execution continues in the background. Use that run id with Get Agent Run to retrieve the latest status and final result. To run the agent synchronously, set `returnImmediately: false` in `data.attributes`. The connection remains open while the agent executes, up to a maximum of 300 seconds. If the run does not complete within that window, the response returns the in-progress run and execution continues in the background. Use the returned run id from `data.id` with Get Agent Run to retrieve the latest status and  Required: agent_id, data.
- **List all ZoomInfo agent runs** (List). List Agent Runs. Lists the run history for a specific agent, with the most recent runs returned first. Use this endpoint to review previous and active runs for the agent. To retrieve the current status and results of a specific run, use Get Agent Run instead. This endpoint does not start or modify a run. Required: agent_id.
- **Get single ZoomInfo agent run by ID** (Get). Get Agent Run. Retrieves the current status and results of a specific agent run. Use the run id returned in `data.id` by Start Agent Run or the first event of a streaming run by Start Agent Run (Stream). By default, the endpoint returns the run's current state immediately. Set `returnImmediately=false` to wait for the run to reach a terminal state. Requests that remain open can wait for up to 300 seconds. If the request times out before the run completes, the response returns the in-progress run and execution continues in the background. Call this endpoint again with the same run id to retrieve the latest status and results. When the run completes, the first item in `artifacts` contains the  Required: id, agent_id.
- **Create a ZoomInfo agent run stream** (Create). Start Agent Run (Stream). Starts a new agent run and streams progress and output over Server Sent Events (`text/event-stream`). The first event includes the runId as `task.id`. Store this value so you can retrieve the run later with Get Agent Run or reconnect using Resume Agent Run Stream. The stream includes status updates and artifact content as the agent runs. The first artifact represents the primary response and may contain text and structured data. A final status update indicates that the run has reached a terminal state. This endpoint is available only for agents that support `STREAMING` in `capabilities.executionModes`. The request uses the same message format and `inputSchema` valid Required: agent_id, data.
- **Get single ZoomInfo agent run stream by ID** (Get). Resume Agent Run Stream. Reconnects to an existing agent run and streams its progress and output using Server-Sent Events (`text/event-stream`). Use this endpoint to reconnect to a run if a Start Agent Run (Stream) connection is interrupted, or to start streaming an existing run that was originally started asynchronously or synchronously using Start Agent Run. When reconnecting, the stream replays the run's existing artifacts from the beginning, then continues with live updates until the run reaches a terminal state. If the run has already completed, it returns the final artifacts and terminal status, then closes the stream. Streaming connections can remain open for up to 300 seconds. If the Required: agent_id, run_id.
- **Get single ZoomInfo account summary by ID** (Get). Get Account Summary. Retrieve the account summary for a specific company. Required: company_id.
- **Create a ZoomInfo account summary question** (Create). Ask Account Summary Question. Ask a question about the account summary of a specific company. Required: company_id, data.
- **ZoomInfo company insights search** (Search). Get insights by type. Retrieve sales intelligence signals for up to 50 companies, filtered by signal type. Signals include funding events, leadership changes, intent spikes, hiring anomalies, and more. # Insights API - Introduction The **Insights API** provides programmatic access to ZoomInfo's curated intelligence layer — actionable data about customer activity that matters most to your business. **Insights** are automatically filtered for relevance, recency, and context based on your team's specific focus areas. This means you receive high-priority updates like decision-maker job changes at target accounts, intent spikes in your buying groups, or website visits from key personas — without  Required: data.
- **List all ZoomInfo company lookalikes** (List). Find Similar Companies. Company Lookalikes 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 lookalike 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. **IMPORTANT: Either `filter[companyId]` or `filter[companyName]` MUST be provided. Omitting both will result in a 422 error.** To find Company Lookalikes, select the `companyId`, which identifies 
- **List all ZoomInfo contact recommendations** (List). Get Contact Recommendations. 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.
- **List all ZoomInfo contact lookalikes** (List). Get Contact Lookalikes. Contact Lookalikes 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, as well as company characteristics such as industry and company size. These lookalike contacts can be used to identify additional stakeholders, expand buyer networks, or build targeted prospecting lists based on known high-priority contacts. To find Contact Lookalikes, select the `referencePersonId`, which identifies the person whose profile you wan
- **List all ZoomInfo buyer personas** (List). List Customer Buyer Personas. Returns the list of Customer Buyer Personas configured for the authenticated customer. A Buyer Persona represents a profile of a key decision-maker or influencer that a company's sales and marketing teams target. Personas capture attributes such as the buyer's role, objectives, priorities, and the motivations that influence purchasing decisions. Personas help organizations align their go-to-market strategy by defining who the ideal buyers are, what problems they care about, and how they should be engaged. Buyer Personas can be connected to products or services with the people most likely to purchase them. If you do not know the ID of the record you need, call Li
- **Create a ZoomInfo buyer persona** (Create). Upsert Customer Buyer Persona. Creates or updates a Customer Buyer Persona. This endpoint performs an upsert operation: If an `id` is included in the request body, the existing persona is updated. Only the fields provided in the request are modified (partial update). If an `id` is not included, a new persona is created. When creating a new persona, `name` is the only required attribute. All other attributes are optional. A Buyer Persona represents a type of buyer that the customer's sales and marketing teams target. Each persona captures key details about the buyer's responsibilities, motivations, and priorities, helping teams tailor messaging and engagement strategies. Buyer Personas can be Required: data.
- **Get single ZoomInfo buyer persona by ID** (Get). Get Customer Buyer Persona. Retrieves a single Customer Buyer Persona by its unique identifier. A Buyer Persona represents a profile of a decision-maker or stakeholder that the customer's sales and marketing teams target. Each persona captures insights into who the ideal buyers are, what motivates them, and how to effectively engage them during the sales process. If the specified buyerPersonaId does not exist, the endpoint returns **404 Not Found**. If you do not know the ID of the record you need, call List Customer Buyer Personas to browse the full set. This endpoint is typically used to retrieve the full configuration of a specific persona before updating or referencing it in downstream w Required: id.
- **Delete a ZoomInfo buyer persona by ID** (Delete). Delete Customer Buyer Persona. Permanently deletes a Customer Buyer Persona identified by `buyerPersonaId`. Deleting a persona removes the associated buyer profile from the system and from any go-to-market configuration that references it. This is a hard delete operation. Once deleted, the persona cannot be recovered. If the specified buyerPersonaId does not exist, the endpoint returns **404 Not Found**. If you want to hide a persona without permanently removing it, use the Archive Customer Buyer Persona endpoint instead. Common use cases - Remove outdated or incorrect personas - Clean up duplicate persona records - Reset persona configuration before recreating it Required: id.
- **ZoomInfo buyer personas archive** (Archive). Archive Buyer Persona. Archives a Customer Buyer Persona. Archiving hides the persona from standard list responses while retaining the record for historical reference, audit compliance, and potential restoration. Archived personas remain stored in the system and continue to count toward customer limits. When a persona is archived, the system sets the metadata fields `archivedAt` and `archivedBy`. This action is reversible. The persona can be restored using the Unarchive Customer Buyer Persona endpoint. Common use cases - Temporarily retire a persona that is no longer actively targeted - Maintain historical records without permanently deleting them - Clean up active persona lists while preser Required: buyer_persona_id.
- **ZoomInfo buyer personas unarchive** (Action). Unarchive Buyer Persona. Restores a previously archived Customer Buyer Persona. Unarchiving makes the persona visible again in standard list responses and allows it to be used again in GTM configuration and workflows. When a persona is restored, the metadata fields `archivedAt` and `archivedBy` are cleared. If the specified buyerPersonaId does not exist, the endpoint returns **404 Not Found**. Common use cases - Reactivate a previously archived persona - Restore a persona that is relevant again for targeting or messaging - Re-enable personas used in go-to-market strategies Required: buyer_persona_id.
- **List all ZoomInfo competitors** (List). List Customer Competitors. Returns the list of Customer Competitors configured for the authenticated customer. A Customer Competitor represents a company that competes with the customer's products or services in the market. Competitor records capture structured competitive intelligence that helps sales and marketing teams understand the competitive landscape and position their products effectively. Competitor profiles may include information such as competing products, win/loss analysis, displacement history, and reasons why deals are won or lost against a particular competitor. A competitor may optionally be linked to a ZoomInfo company record to enable additional enrichment and firmographi
- **Create a ZoomInfo competitor** (Create). Upsert Customer Competitor. Creates or updates a Customer Competitor. This endpoint performs an upsert operation: If an `id` is included in the request body, the existing competitor record is updated. Only the attributes provided in the request are modified (partial update). If an `id` is not included, a new competitor record is created. When creating a new competitor, `name` is the only required attribute. All other attributes are optional. Competitor records store structured competitive intelligence including competing products, win/loss insights, displacement scenarios, and positioning details that help organizations understand how they perform against competitors in the market. Competito Required: data.
- **Get single ZoomInfo competitor by ID** (Get). Get Customer Competitor by ID. Retrieves a single Customer Competitor by its unique identifier. A Customer Competitor represents a company that competes with the customer's products or services. Competitor records capture structured competitive intelligence such as competing products, win/loss analysis, displacement scenarios, and reasons why deals are won or lost against that competitor. A competitor may optionally be linked to a ZoomInfo company record for additional enrichment. If the specified competitorId does not exist, the endpoint returns **404 Not Found**. If you do not know the ID of the record you need, call List Customer Competitors to browse the full set. Common use cases - Retr Required: id.
- **Delete a ZoomInfo competitor by ID** (Delete). Delete Customer Competitor. Permanently deletes a Customer Competitor identified by `competitorId`. Deleting a competitor removes the associated competitive intelligence from the system. This is a hard delete operation and cannot be undone. If the specified `competitorId` does not exist, the endpoint returns **404 Not Found**. If you want to hide a competitor without permanently removing it, use the Archive Customer Competitor endpoint instead. Common use cases - Remove outdated competitor profiles - Clean up duplicate competitor records - Reset competitor data before recreating it Required: id.
- **ZoomInfo competitors archive** (Archive). Archive Customer Competitor. Archives a Customer Competitor. Archiving hides the competitor from standard list responses while retaining the record for historical reference and audit purposes. Archived competitors remain stored in the system and continue to count toward customer limits. When a competitor is archived, the metadata fields `archivedAt` and `archivedBy` are set. This action is reversible using the Unarchive Customer Competitor. Common use cases - Temporarily remove inactive competitors - Preserve historical competitive intelligence - Simplify active competitor lists while retaining records Required: competitor_id.
- **ZoomInfo competitors unarchive** (Action). Unarchive Customer Competitor. Restores a previously archived Customer Competitor. Unarchiving makes the competitor visible again in standard list responses and allows it to be used again in competitive intelligence workflows. When a competitor is restored, the metadata fields `archivedAt` and `archivedBy` are cleared. If the specified `competitorId` does not exist, the endpoint returns **404 Not Found**. Common use cases - Reactivate competitors that are relevant again - Restore archived competitive intelligence records - Re-enable competitors for GTM analysis Required: competitor_id.
- **List all ZoomInfo ideal customer profiles** (List). List Ideal Customer Profiles. Returns a List of Ideal Customer Profile (ICPs) configured for the authenticated customer. An Ideal Customer Profile represents a target company profile that aligns with a company's go-to-market strategy. Each segment defines the types of organizations most likely to benefit from the company's products or services. Segments typically describe target companies using firmographic attributes such as industry, company size, revenue range, geography, and other qualification criteria. These segments help sales and marketing teams focus outreach on the companies most likely to convert. Ideal Customer Profile can be associated with products or services that are targeted
- **Create a ZoomInfo ideal customer profile** (Create). Upsert Ideal Customer Profile. Creates or updates an Ideal Customer Profile. This endpoint performs an upsert operation: If an `id` is included in the request body, the existing segment is updated. Only the attributes provided in the request are modified (partial update). If an `id` is not included, a new segment is created. When creating a new segment, `name` is the only required attribute. All other attributes are optional. An Ideal Customer Profile defines the type of companies that best match the organization’s target market. Segments typically describe firms using firmographic attributes such as industry, company size, revenue range, geography, and other qualification criteria. Common u Required: data.
- **Get single ZoomInfo ideal customer profile by ID** (Get). Get an Ideal Customer Profile. Retrieves a single Ideal Customer Profile by its unique identifier. An Ideal Customer Profile defines the profile of organizations that best match a company's target market. Segments typically describe companies using firmographic attributes such as industry, company size, revenue range, geography, and other qualification criteria. Segments may also include seed companies or structured search filters used for account matching. If the specified segmentId does not exist, the endpoint returns **404 Not Found**. If you do not know the ID of the record you need, call List Ideal Customer Profiles to browse the full set. Common use cases - Retrieve the full configurat Required: id.
- **Delete a ZoomInfo ideal customer profile by ID** (Delete). Delete Ideal Customer Profile. Permanently deletes an Ideal Customer Profile identified by `segmentId`. Deleting a segment removes the associated target company profile from the system and from any go-to-market configuration that references it. This is a hard delete operation and cannot be undone. If the specified `segmentId` does not exist, the endpoint returns **404 Not Found**. If you want to hide a segment without permanently removing it, use the Archive Ideal Customer Profile endpoint instead. Use Get Ideal Customer Profile to verify the profile exists before deletion. Common use cases - Remove outdated or incorrect ICP definitions - Clean up duplicate segments - Reset segment configura Required: id.
- **ZoomInfo ideal customer profiles archive** (Archive). Archive ICP. Archives an Ideal Customer Profile. Archiving hides the segment from standard list responses while retaining the record for historical reference, audit purposes, and possible restoration. Archived segments remain stored in the system and continue to count toward customer limits. When a segment is archived, the system sets the metadata fields `archivedAt` and `archivedBy`. This action is reversible using the Unarchive Ideal Customer Profile endpoint. Common use cases - Temporarily retire an ICP definition - Maintain historical GTM configuration for audit purposes - Simplify active targeting segments without losing data Required: segment_id.
- **ZoomInfo ideal customer profiles unarchive** (Action). Unarchive ICP. Restores a previously archived Ideal Customer Profile. Unarchiving makes the segment visible again in standard list responses and allows it to be used again in GTM targeting and configuration workflows. When a segment is restored, the metadata fields `archivedAt` and `archivedBy` are cleared. If the specified `segmentId` does not exist, the endpoint returns **404 Not Found**. Common use cases - Reactivate previously archived ICP segments - Restore segments that are relevant again for targeting - Re-enable segments used in GTM configuration Required: segment_id.
- **List all ZoomInfo customer settings** (List). Get Customer Settings. Retrieves the customer settings for the authenticated customer. Customer Settings represent the core company-level configuration. This includes foundational information such as the company name, description, elevator pitch, and strategic go-to-market priorities. This information provides the baseline context that AI agents use to generate recommendations, messaging, targeting insights, and account prioritization. This resource is a singleton per customer, meaning each customer can have only one Customer Settings record. If no configuration has been created yet, the endpoint will return **404 Not Found**. Use Post Customer Settings to create or update the settings. Comm
- ...and 63 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
