Skip to main content
Glama

Hunter

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Domain Search

domain_search
Read-onlyIdempotent

Find email addresses for a domain on Hunter.io. Returns the email pattern plus a list of professional/work emails with names, positions, departments, and confidence scores. Example: domain_search({ domain: "stripe.com" })

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by email type: "personal" (named individuals) or "generic" (role addresses like info@)
limitNoMax number of emails to return (default 10, max 100)
domainYesDomain to search, e.g. "stripe.com"
_apiKeyNoOptional — your own Hunter.io API key for higher limits; omit to use the shared Pipeworx key.
departmentNoFilter by department, e.g. "executive", "sales", "engineering"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "domain": "stripe.com"
+  },
+  {
+    "department": "engineering",
+    "domain": "github.com",
+    "limit": 25,
+    "type": "personal"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and not destructive. The description adds value by detailing the return content: email pattern, list with names, positions, departments, and confidence scores, which goes beyond what annotations provide.

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?

Very concise: two sentences plus a useful example. Every part earns its place with no wasted words.

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?

Given the tool has 5 parameters and no output schema, the description covers purpose, return content, and provides an example. It could mention pagination limits or confidence score interpretation, but overall it is fairly complete.

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%, so each parameter is already described. The description adds minimal extra meaning beyond the schema, only an example call. Baseline 3 is appropriate.

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?

The description clearly states it finds email addresses for a domain on Hunter.io, specifying the verb and resource. It is specific but does not differentiate from the sibling tool email_finder, which may have overlapping functionality.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The example implies usage for searching emails by domain, but no when-not-to or alternative suggestions are provided.

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

All Hunter toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources