Skip to main content
Glama

Email Finder

email_finder
Read-onlyIdempotent

Find the most likely professional/work email address for a specific person at a domain on Hunter.io. Returns the email, a confidence score, position, and the number of corroborating sources. Example: email_finder({ domain: "stripe.com", first_name: "Patrick", last_name: "Collison" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "stripe.com",
      "last_name": "Collison",
      "first_name": "Patrick"
    },
    "name": "email_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesCompany domain, e.g. "stripe.com"
_apiKeyNoOptional, your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key.
last_nameYesPerson's last name, e.g. "Collison"
first_nameYesPerson's first name, e.g. "Patrick"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key."New value: +"Optional, your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "domain": "stripe.com",
      +    "first_name": "Patrick",
      +    "last_name": "Collison"
      +  },
      +  {
      +    "domain": "apple.com",
      +    "first_name": "Tim",
      +    "last_name": "Cook"
      +  }
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds value beyond them by disclosing the third-party service (Hunter.io) and, importantly, the return shape — email, confidence score, position, corroborating source count — which tells the agent results are probabilistic rather than guaranteed. It stops short of stating failure behavior (e.g., what happens when no email is found or quotas are hit).

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

Conciseness5/5

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

Two sentences, front-loaded with purpose, followed by return fields and one worked example. Nothing is redundant with the schema and no filler is present.

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?

With no output schema, the description compensates by enumerating the returned fields, and all inputs are documented in the schema. The only remaining gap for a low-complexity, single-lookup tool is error/no-match behavior, which is minor.

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

Parameters3/5

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

Schema coverage is 100% and each of the four parameters already has a description with an example, including the optional _apiKey for higher limits. The description's concrete example call shows the parameters in combination but adds no semantic detail the schema lacks, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb+resource ('find the most likely professional/work email address for a specific person at a domain') and names the provider (Hunter.io), which is far more precise than the title alone. It does not explicitly differentiate itself from the sibling email_verifier (find vs. verify), so it falls short of a 5.

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

Usage Guidelines3/5

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

The phrasing implies the use case (you have a person's name and company domain and want their email), and the example call reinforces the required input pattern. However, there is no explicit when-to-use/when-not guidance and no mention of email_verifier as the alternative for validating an already-known address.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.