Search for recorded calls in Gong within a date range.

Returns a list of calls with metadata: title, date, duration, participants, and Gong URL. Use this to find calls for a specific time period, then use gong_get_call_details or gong_get_transcript for deeper analysis.

Args:

• from_date (string): Start date in ISO 8601 (e.g. '2024-01-01T00:00:00Z')

• to_date (string): End date in ISO 8601 (e.g. '2024-02-01T00:00:00Z')

• workspace_id (string, optional): Gong workspace ID to scope results

• cursor (string, optional): Pagination cursor from previous response

• response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of calls with title, date, duration, direction, participants, and URL.

Examples:

• "Find all calls last week" -> from_date='2024-01-08T00:00:00Z', to_date='2024-01-15T00:00:00Z'

• "Get recent demo calls" -> search calls then filter by title containing 'demo'

Retrieve the full transcript of a specific Gong call.

Returns timestamped sentences with speaker identification. Use gong_search_calls first to find call IDs.

Args:

• call_id (string): The Gong call ID

• response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Timestamped transcript with speaker labels.

Examples:

• "Get the transcript for call 123456" -> call_id='123456'

Get detailed analytics for a specific Gong call — topics discussed, trackers triggered, action items, talk ratios, and speaker stats.

Use gong_search_calls first to find call IDs.

Args:

• call_id (string): The Gong call ID

• response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Call metadata, topics, trackers, action items, interaction stats, and speaker breakdown.

Examples:

• "Analyze call 123456" -> call_id='123456'

• "What topics were discussed in call 789?" -> call_id='789'

Find Gong calls where a specific person participated, identified by their email address.

Useful for pulling a prospect's or rep's recent call history.

Args:

• email (string): Email address of the participant

• from_date (string): Start date in ISO 8601

• to_date (string): End date in ISO 8601

• response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: List of calls the participant was on.

Examples:

• "Find calls with john@acme.com in January" -> email='john@acme.com', from_date='2024-01-01T00:00:00Z', to_date='2024-02-01T00:00:00Z'

Get aggregate call statistics for a date range — total calls, average duration, and call breakdown.

Useful for pipeline reviews and rep activity analysis.

Args:

• from_date (string): Start date in ISO 8601

• to_date (string): End date in ISO 8601

• response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Total calls, average duration, direction breakdown, and top participants.

Examples:

• "How many calls did we have last month?" -> set appropriate from/to dates

Search the ZoomInfo database for companies by name, domain, industry, size, or revenue.

Returns firmographic data: employee count, revenue, industry, location, and description. Use the returned company ID for zoominfo_get_org_chart or zoominfo_get_tech_stack.

Args:

• company_name (string, optional): Company name (partial match)

• domain (string, optional): Website domain (e.g. 'acme.com')

• industry (string, optional): Industry filter

• min_employees / max_employees (number, optional): Employee count range

• min_revenue (number, optional): Minimum annual revenue in USD

• country (string, optional): Country filter

• limit (number): Max results (default: 20, max: 100)

• page (number): Page number (default: 1)

• response_format ('markdown' | 'json')

Returns: Company name, website, industry, employee count, revenue, location, founded year.

Examples:

• "Find Acme Corp" -> company_name='Acme'

• "SaaS companies with 500+ employees" -> industry='Technology', min_employees=500

Search the ZoomInfo database for contacts by name, title, department, company, or management level.

Returns contact details: name, title, email, phone, company, LinkedIn, and location. Use for prospecting, building contact lists, or enriching CRM records.

Args:

• first_name / last_name (string, optional): Contact name

• email (string, optional): Email address

• job_title (string, optional): Title keyword (e.g. 'VP Sales')

• management_level (string, optional): 'c-level', 'vp-level', 'director', 'manager', 'staff'

• department (string, optional): Department (e.g. 'Sales', 'Engineering')

• company_name / company_domain (string, optional): Scope to a company

• limit (number): Max results (default: 20)

• page (number): Page number (default: 1)

• response_format ('markdown' | 'json')

Returns: Contact name, title, email, phone, department, level, company, location, LinkedIn.

Examples:

• "Find VP of Sales at Acme" -> job_title='VP Sales', company_name='Acme'

• "C-level contacts in engineering" -> management_level='c-level', department='Engineering'

Get the organizational chart for a company from ZoomInfo — shows reporting hierarchy, departments, and management levels.

Use zoominfo_search_company first to get the company ID.

Args:

• company_id (number): ZoomInfo company ID

• department (string, optional): Filter to a specific department

• response_format ('markdown' | 'json')

Returns: Hierarchical list of contacts with titles, departments, management levels, and reporting lines.

Examples:

• "Org chart for company 12345" -> company_id=12345

• "Engineering leadership at company 12345" -> company_id=12345, department='Engineering'

Get the technology stack used by a company — CRM, marketing automation, analytics, cloud infrastructure, etc.

Provide either company_id or domain.

Args:

• company_id (number, optional): ZoomInfo company ID

• domain (string, optional): Company domain (e.g. 'acme.com')

• response_format ('markdown' | 'json')

Returns: List of technologies categorized by type.

Examples:

• "What tech does acme.com use?" -> domain='acme.com'

• "Tech stack for company 12345" -> company_id=12345

Enrich a person's profile using Clay's data network — returns job title, company, email, phone, LinkedIn, location, and bio.

Provide at least one of: email, linkedin_url, or first_name + last_name + company_domain.

Args:

• email (string, optional): Person's email (best lookup key)

• linkedin_url (string, optional): LinkedIn profile URL

• first_name / last_name (string, optional): Name for fuzzy matching

• company_domain (string, optional): Company domain for disambiguation

• response_format ('markdown' | 'json')

Returns: Full name, title, company, email, phone, LinkedIn, location, bio.

Examples:

• "Enrich john@acme.com" -> email='john@acme.com'

• "Find info on Jane Doe at acme.com" -> first_name='Jane', last_name='Doe', company_domain='acme.com'

Enrich a company profile using Clay's data network — returns industry, employee count, revenue, tech stack, funding, and description.

Provide domain (preferred) or company_name.

Args:

• domain (string, optional): Company website domain (best lookup key)

• company_name (string, optional): Company name (fallback)

• response_format ('markdown' | 'json')

Returns: Company name, domain, industry, employees, revenue, founded, location, funding, tech stack, description.

Examples:

• "Enrich acme.com" -> domain='acme.com'

• "Get info on Acme Corp" -> company_name='Acme Corp'

Send data to a Clay webhook to trigger a table-based enrichment workflow.

Clay tables run custom enrichment sequences (waterfall emails, phone lookups, intent signals, etc.). The webhook URL is unique to each Clay table — get it from your Clay table settings.

Args:

• webhook_url (string): The Clay webhook URL for the enrichment table

• data (object): Key-value pairs to send (e.g. { "email": "john@acme.com", "company": "Acme" })

• response_format ('markdown' | 'json')

Returns: Confirmation that data was submitted. Enrichment runs asynchronously — results appear in your Clay table.

Examples:

• Trigger enrichment: webhook_url='https://...', data={"email":"john@acme.com","name":"John Doe"}

Search for people/leads on LinkedIn using keywords, title, company, seniority, geography, and industry filters.

Uses the standard LinkedIn REST API (no SNAP partnership required). Works with any LinkedIn developer token that has the appropriate OAuth scopes.

Note: The standard LinkedIn API has more limited people search than Sales Navigator. For deep lead research, combine with ZoomInfo or Clay enrichment tools.

Args:

• keywords (string, optional): Free-text search across profiles

• first_name / last_name (string, optional): Name filters

• title (string, optional): Job title filter

• company_name (string, optional): Current company

• industry (string, optional): Industry

• geography (string, optional): Location/region

• seniority (string, optional): 'owner', 'cxo', 'vp', 'director', 'manager', 'senior', 'entry'

• limit (number): Max results (default: 20)

• offset (number): Pagination offset

• response_format ('markdown' | 'json')

Returns: Name, headline, title, company, location, industry, profile URL.

Examples:

• "VP Engineering in Bay Area" -> title='VP Engineering', geography='San Francisco Bay Area'

• "CTO at Acme Corp" -> title='CTO', company_name='Acme Corp'

Get LinkedIn profile information for a specific person.

Uses the standard LinkedIn REST API (no SNAP required). Provide either a LinkedIn URL or member ID.

If neither is provided, returns the authenticated user's own profile.

Args:

• linkedin_url (string, optional): LinkedIn profile URL

• member_id (string, optional): LinkedIn member ID

• response_format ('markdown' | 'json')

Returns: Full profile with headline, title, company, location.

Examples:

• "Get profile for linkedin.com/in/johndoe" -> linkedin_url='https://linkedin.com/in/johndoe'

• "Get my LinkedIn profile" -> (no params, returns authenticated user)

Search for companies on LinkedIn by name, industry, size, or geography.

Uses the standard LinkedIn REST API (no SNAP required).

Args:

• keywords (string, optional): Free-text company search

• company_name (string, optional): Company name

• industry (string, optional): Industry filter

• min_employees / max_employees (number, optional): Size range

• geography (string, optional): HQ location

• limit (number): Max results (default: 20)

• offset (number): Pagination offset

• response_format ('markdown' | 'json')

Returns: Company name, industry, size, HQ, website, specialties, description.

Examples:

• "SaaS companies in San Francisco" -> keywords='SaaS', geography='San Francisco'

• "Find Acme Corp on LinkedIn" -> company_name='Acme Corp'

Check which sales intelligence services are configured and available.

Returns the configuration status of each integrated service (Gong, ZoomInfo, Clay, LinkedIn). Use this to verify which tools are ready to use before running queries.

Args: None

Returns: Status of each service (configured/not configured) with required environment variables.