Skip to main content
Glama

Snov Domain Email Count

snov_domain_email_count
Read-onlyIdempotent

How many email addresses does Snov.io have for a domain?, a free pre-check before spending credits on a full snov_domain_search. Example: snov_domain_email_count({ domain: "riotgames.com", _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": {
      "domain": "riotgames.com",
      "_apiKey": "your-snov-client_id:your-snov-client_secret"
    },
    "name": "snov_domain_email_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavior context: the call is free and does not consume credits, which is the key decision input. It does not explain what the count represents (total harvested addresses vs. verified only) or how it relates to search result volume.

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?

Two short sentences with the cost-saving rationale front-loaded, plus a compact example. The opening phrasing ("...for a domain?,") is grammatically awkward and the example duplicates the schema's own examples field, which is minor waste.

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 two-parameter read-only lookup, the definition covers purpose, cost behavior, and parameter formats. With no output schema, it would help to indicate the return shape (a single count value), but the tool's question-form framing makes the expected result inferable.

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%, with both `domain` (no protocol) and `_apiKey` (client_id:client_secret, paid plan required) documented in the schema itself. The inline example restates the same formats rather than adding meaning, so the baseline 3 applies.

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 states a specific verb+resource (counting email addresses Snov.io holds for a domain) and explicitly distinguishes it from the sibling snov_domain_search by framing it as a pre-check rather than a full search. An agent can identify the tool's job without opening the schema.

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?

"a free pre-check before spending credits on a full snov_domain_search" gives a clear when-to-use condition and names the alternative that consumes credits. It stops short of explicit when-not guidance (e.g., skipping the check when a full search is needed anyway), but the routing intent is unambiguous.

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.