Skip to main content
Glama

Snov Domain Search

snov_domain_search
Read-onlyIdempotent

Find every email address on a company domain, "who works at riotgames.com and what are their emails?". Returns emails with first/last name, job position, and type (personal or generic), plus company info, from Snov.io. Complements Hunter domain search. Example: snov_domain_search({ domain: "riotgames.com", limit: 50, _apiKey: "client_id:client_secret" })

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": {
      "limit": 50,
      "domain": "riotgames.com",
      "_apiKey": "your-snov-client_id:your-snov-client_secret"
    },
    "name": "snov_domain_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhich emails to return: "all" (default), "personal", or "generic".
limitNoMax emails to return (default 20, max 50).
domainYesCompany domain, no protocol, e.g. "riotgames.com"
_apiKeyYesSnov.io OAuth credentials as "client_id:client_secret" from app.snov.io/account/api (paid plan required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is carried for it. The description adds useful return-shape disclosure (name, position, personal vs generic type, company info) since there is no output schema, but says nothing about credit/rate cost, coverage limits, or result ordering.

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 purpose and return fields are front-loaded in the first two sentences, with the example last where it belongs. The Hunter comparison and the example partially duplicate what already exists in the schema examples, so it is slightly longer than necessary but not padded.

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 a four-parameter read-only lookup with no output schema, the description covers what the tool does and what comes back, which is the key gap. It leaves cost and pagination behavior unstated, but an agent can call it correctly from what is given.

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 an enum-like listing for type and the min/max for limit, so the schema does the heavy lifting. The description's inline example reiterates domain, limit and _apiKey but adds no new semantics such as what happens when limit exceeds available emails.

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 definition states a specific verb and resource ("Find every email address on a company domain") and enumerates the returned fields, so the agent knows exactly what it gets. It notes that it "Complements Hunter domain search" but that is a third-party analogy rather than routing help against siblings like snov_domain_email_count, which is never mentioned.

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 natural-language question ("who works at riotgames.com and what are their emails?") implies the use case, and an example call shows invocation. However, there is no explicit statement of when to prefer this over snov_domain_email_count or Hunter, and no exclusions or prerequisites beyond the paid-plan note that lives in the schema.

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.