Skip to main content
Glama

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" })

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"
    },
    "name": "domain_search"
  }
}

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
    • 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"
      +  },
      +  {
      +    "department": "engineering",
      +    "domain": "github.com",
      +    "limit": 25,
      +    "type": "personal"
      +  }
      +]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the upstream provider and enumerating the returned fields, but says nothing about credit consumption, rate limits, empty-result behavior, or pagination beyond the limit cap.

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?

Front-loaded with the core action, then the return shape, then a compact inline example — all in three short sentences. Minor redundancy in 'professional/work emails,' but nothing that wastes meaningful space.

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 usefully compensates by enumerating the return fields, and the example clarifies the minimal call. Gaps remain around failure/empty cases and the shared-vs-personal API key tradeoff, but for a five-parameter read-only lookup it is close to sufficient.

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 description coverage is 100%, including enum values and default/max for limit, so the schema does the heavy lifting. The description only supplies an illustrative example call, which adds slight clarity but no semantic detail beyond what the schema documents.

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 and resource ('Find email addresses for a domain on Hunter.io') and even describes the return payload (email pattern, names, positions, departments, confidence scores). It does not, however, distinguish itself from sibling tools like email_finder or email_verifier, so an agent must infer the boundary.

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?

Usage is only implied by the purpose statement: use this when you have a domain and want associated emails. There is no explicit when-to-use/when-not, no mention of when email_verifier or email_finder would be preferable, and no note about cost or quota consumption when calling.

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.