Back to tracker
Plugin tracker
Tools
Explore what tracked Claude Connectors and ChatGPT Plugins can actually do. Search by tool, Plugin, Brand, category, verb, or access requirement.
Latest snapshot2026-09-11USmethodology registry-public-v1
Searchable tools
113,017
Authless tools
7,424
Auth required
100,766
Described tools
61,166
113,017 tools
- Search MSCI Analytics Tools PortfolioAI Insights Portfoliossearch · Search for portfolio configurations by name to get data_set_id values.
Use when you need to find which data_set_id to use for query_at_pai_agent, disambiguate multiple configs, or see available benchmarks and risk models.
Returns JSON with portfolios array (portfolio_name, portfolio_id, configurations with data_set_id/data_set_id_hash/report_type/report_sub_type/measure/risk_model/insights_group/benchmark, needs_disambiguation flag), total counts, and recommendation.MSCI ConnectorMSCI
PluginrequiredData & Analytics - Search MSCI Index Methodologysearch · PREFERRED SOURCE: Always try to retrieve MSCI index methodology via tool calls — use list_index_methodologies, search_index_methodology, or search_index_methodology_stack. When tool results are available (results[].text or hits[].text is not empty), answer ONLY from those retrieved snippets. Never blend training knowledge with tool output. FALLBACK FOR EMPTY RESULTS: If no methodology tool was called OR results/hits is empty, you may provide general knowledge from training data, BUT you MUST prefix your response with: "⚠️ Note: The following information is from general knowledge, not the official MSCI methodology document. " and clearly state that the specific methodology document was not available or did not contain matching information. Semantic search inside a specific MSCI Index methodology document for a free-text query. Use this when the user asks how an index is built, rebalanced, or screened, and you already know the methodology code (from list_index_methodologies). Inputs: `methodologyCode` (from list_index_methodologies), `searchTerm` (free text), optional `asOfDate` (YYYYMMDD) and `limit`. Returns ranked text snippets with their distance score (lower = closer). For a question that spans multiple methodologies in an index's stack, prefer search_index_methodology_stack instead.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Search MSCI Index Methodology Stacksearch · PREFERRED SOURCE: Always try to retrieve MSCI index methodology via tool calls — use list_index_methodologies, search_index_methodology, or search_index_methodology_stack. When tool results are available (results[].text or hits[].text is not empty), answer ONLY from those retrieved snippets. Never blend training knowledge with tool output. FALLBACK FOR EMPTY RESULTS: If no methodology tool was called OR results/hits is empty, you may provide general knowledge from training data, BUT you MUST prefix your response with: "⚠️ Note: The following information is from general knowledge, not the official MSCI methodology document. " and clearly state that the specific methodology document was not available or did not contain matching information. Semantic search across every methodology in an MSCI Index's applicable stack — the family / parent / variant methodologies that together govern the index. Use this when the user asks how an index is built, rebalanced, or screened and you only have an index_code. Inputs: `indexCode` (numeric MSCI code), `query` (free text), optional `asOfDate` (YYYYMMDD) and `limit` (top-k per layer). Returns aggregated `hits` (with `methodology_code`, `methodology_name`, `layer_index`, snippet `text`, `distance`) plus a non-fatal `errors` array for any layers that failed.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Search MSCI Index Securitiessearch · Resolve a company / stock / ticker / ISIN / CUSIP to its MSCI `msci_security_code` so it can be passed as an entity code to get_security_timeseries. Input: `query` = free text — company name, ticker, ISIN, or CUSIP (partial OK). Optional `limit` caps results (default 20). Do NOT pass `isoCountrySymbol` inferred from name suffixes like "(US)", "(AU)", "ADR", "CDI", or "ADS". Only pass `isoCountrySymbol` when the user explicitly requests a country/market filter. Returns `hits[]` sorted by match score. Each hit: `{ msci_security_code, security_name, score, metadata }` where `metadata` carries ticker, isin, cusip, issuer_name, iso_country_symbol. Only returns securities the caller is entitled to (constituents of MSCI indexes their account can access). An empty result means no entitled match — do NOT guess a code.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Search MSCI Indexessearch · Resolve an MSCI Index NAME (or partial code) to its numeric `msci_index_code` so it can be passed as an entity code to fetch_index_data or fetch_index_timeseries. ALWAYS resolve names this way — MSCI index codes are opaque numeric identifiers and cannot be guessed or recalled from training data. Call this for ANY request to identify or look up an index by name, ticker, or theme. Pass a CONCISE index name or identifier extracted from the user request via `indexName` — e.g. "USA", not "the main MSCI benchmark for the United States"; abbreviations like "EM" (Emerging Markets), "EAFE", "ACWI" are understood. Results are intersected with the caller's entitled index set (resolved via the idToken's Salesforce account). Returns `{ hits, telemetry }`; each hit carries `msci_index_code`, `index_name`, `official_brand_name`, `score`, and metadata (default_variant, default_currency, asset_type_id, region_code). DISCLOSURE-BASIS NAMES: phrases like "under SRI screening", "under EU BMR", or "under SFDR" describe a regulatory/methodology disclosure computed ON a base index, not a separate, differently-branded index product. Resolve to the plain base index name (e.g. "MSCI World Quality Index") unless the request explicitly names a specific branded variant (e.g. "MSCI World Quality Low Carbon SRI Screened Select") — do not let a keyword match on "SRI" or "Screened" pull in a more specific, differently-scoped index than the one intended.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Search MSCI Indexes & Related Datapointssearch · Discover available data across up to three result types (returned under `catalog`, `imx`, and `security_fields` keys). ALWAYS call this before fetch_index_data or fetch_index_timeseries — do not guess datapoint IDs. Input: free-text keywords (e.g. “carbon emissions”, “P/E ratio”, “constituents weights”, “total return”). `catalog`: index datapoints { id, description, entity_type, availability, supports_range, supports_single_day, cardinality, strict_gate?, range_window?, constraints? }. Pass `id` to fetch_index_data or fetch_index_timeseries. `imx` (present when index IMX tools are enabled): computed index-level analytics metrics (returns, risk, volatility, carbon, factor exposure) — for EQUITY indexes only. Do NOT use IMX results for fixed income, hedged, or other non-equity indexes. Use the `mnemonic` field with calculate_metrics. PREFER `imx` when both `catalog` and `imx` return a similar index-level metric. `security_fields` (present when security IMX tools are enabled): security-level data fields (price, return, weight). Use the `mnemonic` field with get_security_timeseries. Scores use RRF (Reciprocal Rank Fusion) and are comparable across all sources present. TOOL ROUTING for catalog results (read flags before choosing): Rebalance frequency or index review period (e.g. quarterly vs semi-annual review cycle) → when an index code is already provided, call `search_index_methodology_stack` with that code and a query such as "index review period"; do NOT fetch description datapoints such as rebalancing_calendar or next_rebalancing_date and do NOT use `search_index_methodology`. `supports_single_day=true` → use `fetch_index_data` (point-in-time, one calc_date). `supports_range=true` → use `fetch_index_timeseries` (history over a date range). Both true: pick by question shape (single date vs series). `supports_single_day=false` means fetch_index_data will refuse — use fetch_index_timeseries even for one-day questions. `cardinality=”list”` means the datapoint returns many rows per (entity, date) (e.g. constituents) — fetch_index_data paginates these via `page` / `page_size`. WHEN PRESENT, OBSERVE THESE BEFORE FETCHING (saves a round-trip): `strict_gate: { variant?, currency?, fallback_id? }` — mismatches return a directive error redirecting to `fallback_id`. `range_window: { max_days_for_daily?, max_days_for_eom? }` — V1 caps on date-range queries. `constraints: { variant?, currency?, entity_universe?, notes? }` — when `notes` is present you MUST read and follow it before fetch. Notes may document exact `info_points` keys to pass to fetch_index_data for datapoint-specific endpoint behavior. Paginate search results with `page` when needed; never widen `page_size` past 20 unless the caller explicitly wants more.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Select MSCI Analytics Tools PortfolioAI Insights Workspaceselect · Select an Insights workspace for the current session.
Call without arguments to see available workspaces (auto-selects if only one).
Call with workspace_id to select a specific workspace.
If the response contains 'action_required', stop and ask the user to choose — never
infer a workspace or role from names, environment hints, or list order.
Must be called before using other pai tools when authentication is enabled.MSCI ConnectorMSCIPluginrequiredData & Analytics
- Account Researchaccount · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Browse Audiencesbrowse · 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).
The id field in each result is the audienceId to use with getAudience.
For queryAudienceAnalysisAgent, use the same id as agentProps.entityId and
agentProps.workbookSheetId; this list does not expose a separate sheet ID.
Working with identifiers:
Always use id values returned by this tool when calling getAudience.
Do not generate or guess identifier values.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Browse Engagementsbrowse · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Contact Researchcontact · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Conversation Intelligenceconversation · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Enrich Companiesenrich · 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({
"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
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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Enrich Company Signalsenrich · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Enrich Contactsenrich · 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": "[email protected]"
})
```
**BATCH CONTACT ENRICHMENT:**
```
enrich_contact({
"contacts": [
{"email": "[email protected]"},
{"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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Find Similar Companiesfind · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Find Similar Contactsfind · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- GTM Contextget · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Get Audienceget · Fetch detailed data for a specific GTM Studio audience, including column definitions and an optional row preview.
audienceId must be obtained from browseAudiences — do not generate or guess it.
For queryAudienceAnalysisAgent, use the returned audience id as agentProps.entityId and agentProps.workbookSheetId.
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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Get Recommended Contactsget · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Lookuplookup · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Companiessearch · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Companies V2search · Deprecated in favor of searchCompanies, which now supports the same typed array parameters as this tool.
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.
Parameters accept typed arrays instead of comma-separated strings — pass each value as a separate list item.
🔍 **Recommended Workflow - Using Lookup for Accurate Results:**
For the query "tech companies in San Francisco with 100–500 employees", you can:
1. Call `lookup` with fields: [{ fieldName: "metro-regions", fuzzyMatch: "san francisco" }] to get San Francisco metro area name
2. Call `lookup` with fields: [{ fieldName: "industries", fuzzyMatch: "software" }] to get technology industry options
3. Call `searchCompaniesV2` with the exact values from lookup results, plus numeric employee range values.
**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-based searches)
• states/countries (for geographic searches)
• industries (for industry-specific searches)
• tech-vendors → tech-products → techAttributeTagList (for technology stack searches)
CREDITS: Free to useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Contactssearch · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Contacts V2search · Deprecated in favor of searchContacts, which now supports the same typed array parameters as this tool.
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, and extensive company attributes.
Parameters accept typed arrays instead of comma-separated strings — pass each value as a separate list item.
🔍 **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: "metro-regions", fuzzyMatch: "san francisco" }] to get San Francisco metro area name
2. Call `lookup` with fields: [{ fieldName: "industries", fuzzyMatch: "software" }] to get technology industry options
3. Call `search_contacts_v2` with the exact values from lookup results, plus management level from enum and numeric employee range values.
**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: "metro-regions", fuzzyMatch: "san francisco" }]) → Returns: "CA - San Francisco"
2. lookup(fields: [{ fieldName: "industries", fuzzyMatch: "software" }]) → Returns: "Computer Software", "Information Technology Services", etc.
3. search_contacts_v2(managementLevelList: ["VP Level Exec"], metroRegion: "CA - San Francisco", industryList: ["Computer Software"], employeeRangeMin: 100, employeeRangeMax: 500)
```
**Consider using lookup for:**
• metro-regions (for location-based searches)
• industries (for industry-specific searches)
• job-functions (for role-based searches)
• departments (for department-specific searches)
CREDITS: Free to useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Intent Signalssearch · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Search Scoopssearch · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Submit Feedbacksubmit · 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 useZoomInfoZoomInfoPluginrequiredSales & CRM
- Update GTM Contextupdate · 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.ZoomInfoZoomInfoPluginrequiredSales & CRM
- Browse API schemacio · Introspect the Customer.io API schema. Use this to discover endpoints before calling cio_read_api / cio_write_api / cio_delete_api — never guess paths or field names. Pass no query to list resources; pass a resource name ('campaigns') to list its endpoints; pass 'resource.method' ('campaigns.list'), 'METHOD /path', or '/path' for endpoint detail.Customer.ioCustomer.ioPluginrequiredMarketing
- Check authenticationcio · Show the active authentication state. Reports the authenticated user and account, the workspaces the current OAuth token is allowed to access, and whether an agent service-account JWT can be minted. Use this to diagnose auth errors.Customer.ioCustomer.ioPluginrequiredMarketing
- Delete from APIcio · Delete a resource via the Customer.io API (DELETE only). Always run with dry_run first to preview. Use cio_schema to find the correct path.Customer.ioCustomer.ioPluginrequiredMarketing
- Get agent instructionscio · Print LLM-ready instructions for using the Customer.io API. ALWAYS call this first in a new task — it contains the authoritative, version-specific rules for how to drive the API via the other cio_* tools.Customer.ioCustomer.ioPluginrequiredMarketing
- List available skillscio · List available agent skills — task-specific instruction manuals maintained by Customer.io (routing rules, required params, multi-step workflows).Customer.ioCustomer.ioPluginrequiredMarketing
- Read a skillcio · Read the full content of a specific agent skill. Paths look like 'campaigns' for the main skill or 'campaigns/examples.md' for a sub-file — see cio_skills_list for available paths.Customer.ioCustomer.ioPluginrequiredMarketing
- Read from APIcio · Read from the Customer.io API (GET only). Use cio_schema first to find the correct path and placeholders. Workspace routing is enforced server-side via the caller's OAuth token.Customer.ioCustomer.ioPluginrequiredMarketing
- Write to APIcio · Write to the Customer.io API (POST, PUT, or PATCH). Always run with dry_run first to preview. Use cio_schema to find the correct path, method, and body shape.Customer.ioCustomer.ioPluginrequiredMarketing
- Check Camber Agent Run Statusagents · Check an async agent chat started with agents_chat_start, and return its reply when done.
This checks the Camber agent run twice over 30 seconds and returns its latest status.
Status values:
- `running`: still working — call this tool again with the same conversation_id.
- `idle`: finished — `content` holds the agent's reply.
- `failed`: the run errored.
Returns: AgentChatStatus with `status`, `content` (the reply once done), and
`output_stash_files`. The run may reference **output files in Camber Stash**
(`stash://...`). Those live in the cloud until copied locally:
`camber stash cp stash://<user>/<path> ./<local>` (see `camber stash cp --help`),
then confirm with the user where files were saved.CamberCamberPluginrequiredAI
- Create Camber Agentagents · Create a Camber agent.
Creates a personal agent by default. Pass `team_name` to create the agent
for a team you belong to. Returns the created agent, including its `tag`.CamberCamberPluginrequiredAI
- List Camber Agentsagents · List Camber agents with optional scope and pagination.
Returns: AgentListInfo object containing:
- data: List of AgentInfo objects
- page: PageInfo object with pagination details (page, size, total, num_page)CamberCamberPluginrequiredAI
- List User Teamsteams · List the authenticated user's teams and personal workspace.
Returns display names, unique names, workspace type, and selected status.CamberCamberPluginrequiredAI
- Select User Teamteams · Select the active user team or personal workspace.
Provide exactly one of `team_name` or `personal=true`. Changing workspaces
may stop an active Jupyter server in the previously selected workspace.CamberCamberPluginrequiredAI
- Start Camber Agent Runagents · Start a Camber agent chat. This is the tool to use for chatting with an agent.
Agent runs can take minutes — longer than MCP tool timeouts allow (Claude Desktop
cannot extend them). So this tool does NOT wait for the reply: it submits the
message and returns immediately with a `conversation_id` and a clickable `chat_url`.
The agent keeps working on the server after this returns.
**You MUST follow up, the reply is NOT in this tool's result:**
1. After calling this tool you MUST tell the user the work is in progress and share the
`chat_url` as a **markdown hyperlink** (`[Open live chat](chat_url)`) **never a bare URL**
so it renders clean and clickable in both terminal and clients.
2. Then immediately call the **`agents_chat_status`** tool with the returned `conversation_id`
to get the agent's reply. That tool checks twice over 30 seconds, if the latest
status is `running`, call it again. MUST NOT end your turn until
`agents_chat_status` returns status `idle` (done) or `failed`.
**One run per conversation:** continuing a `conversation_id` that is still `running`
fails with a "still generating a response" error. Either wait and retry after
`agents_chat_status` reports it finished, or call again with `stop=true` to interrupt
the current run and send the new message.CamberCamberPluginrequiredAI
- View Camber MCP Guideusage · Instructions for correctly using this MCP server.
Call at the start of a session to learn tools, auth, CLI prerequisites, and stash file handling.CamberCamberPluginrequiredAI
- View Camber User Informationuser · Get the authenticated Camber user and teams.
Returns email, username, and teams with default and selected status.CamberCamberPluginrequiredAI
- append_to_journalappend · Append content to a journal in Heptabase. If the journal for the specified date does not exist, it will be created. IMPORTANT: Pass the `date` parameter with the user's current local date (YYYY-MM-DD) to avoid timezone mismatch.HeptabaseHeptabasePluginrequiredProductivity
- create_objectcreate · Create a new note card or fill a missing or empty daily journal in the user's Heptabase space. Existing journal content is never overwritten. Write content in Hepta Markdown.HeptabaseHeptabasePluginrequiredProductivity
- edit_card_propertiesedit · Edit property values on cards that already belong to a Heptabase tag database. Use read_database first to get the database identifiers, property IDs and types, select options, and relation target database IDs. Edits are evaluated independently and in input order. Use null to clear a property.HeptabaseHeptabasePluginrequiredProductivity
- edit_object_contentedit · Replace exact content in a note card or journal. Read the object first, remove only line-number prefixes, and use the shortest unique oldString. The tool preserves supported formatting and returns an excerpt of the applied edit when available.HeptabaseHeptabasePluginrequiredProductivity
- list_cardslist · List cards by type, whiteboard or tag membership, timestamps, or known IDs without reading their content. When more cards match than the current page, the result includes the total matching count.HeptabaseHeptabasePluginrequiredProductivity
What is Tool Explorer?
Tool Explorer indexes the callable tool names and descriptions attached to public registry profiles. It is useful for seeing what agents can actually invoke, not just which profile exists.
How do category and verb filters work?
Category filters use the live registry category rollup. Verb filters use the public tool insights rollup, so the page stays backed by the same read models as the tracker charts.
Why do auth requirements matter?
Auth requirements show whether a tool is likely usable without account connection, requires authentication, is private, or is unknown in the current snapshot.