Skip to main content
Glama
jbalbu01

sales-intelligence

by jbalbu01

Search ZoomInfo Contacts

zoominfo_search_contact
Read-onlyIdempotent

Discover B2B contacts by name, title, department, or company. Retrieve emails, phones, and LinkedIn profiles to build prospect lists and enrich CRM records.

Instructions

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'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
emailNoContact email address
limitNoMaximum results to return
job_titleNoJob title keyword (e.g. 'VP Sales', 'CTO')
last_nameNoContact's last name
departmentNoDepartment filter (e.g. 'Sales', 'Engineering', 'Marketing')
first_nameNoContact's first name
company_nameNoCompany name to scope the contact search
company_domainNoCompany domain to scope the contact search
response_formatNoOutput format: 'markdown' or 'json'markdown
management_levelNoManagement level: 'c-level', 'vp-level', 'director', 'manager', 'staff'
Behavior3/5

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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds return fields and response formats, but does not disclose rate limits, data freshness, authentication requirements, or other behavioral caveats. Given the strong annotation coverage, a 3 is appropriate.

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

Conciseness4/5

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

The description is well-structured with a clear summary, use cases, parameter list, and examples. However, the return fields are listed twice ('Returns contact details...' and 'Returns: Contact name...'), which is mildly redundant and prevents a perfect score.

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

Completeness4/5

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

For an external search tool with 11 parameters and no output schema, the description covers purpose, usage, all parameters, and return fields, and it provides practical examples. It could be more complete by explicitly distinguishing when to use this tool versus sibling contact-enrichment tools, but overall it is quite thorough.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value with concrete examples like 'Find VP of Sales at Acme' -> job_title='VP Sales', company_name='Acme' and enumerates valid management_level values. These examples go beyond the schema descriptions and help clarify parameter usage.

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

Purpose5/5

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

The description opens with 'Search the ZoomInfo database for contacts by name, title, department, company, or management level' — a specific verb + resource + filter criteria. This clearly distinguishes it from sibling tools like zoominfo_search_company, which focuses on companies rather than contacts.

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

Usage Guidelines4/5

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

It explicitly states 'Use for prospecting, building contact lists, or enriching CRM records,' giving clear usage context. However, it does not mention when not to use it or how it compares to alternatives like linkedin_search_leads or clay_enrich_person, so it falls short of a perfect 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jbalbu01/sales-intelligence-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server