Skip to main content
Glama

Snov Email Profile

snov_email_profile
Read-onlyIdempotent

Look up the person behind an email address, "who is john@stripe.com?". Returns the contact's name, current job title and employer, industry, location, and linked social profiles via Snov.io email enrichment. Example: snov_email_profile({ email: "john@stripe.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": {
      "email": "john@stripe.com",
      "_apiKey": "your-snov-client_id:your-snov-client_secret"
    },
    "name": "snov_email_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to enrich, e.g. "john@stripe.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, openWorld and non-destructive, so the safety profile is covered. The description adds useful context by naming the enrichment provider and listing the returned attributes, but says nothing about failure behavior (unknown email), credit consumption, or rate limits for a paid external API.

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 purpose in the first clause, followed by return fields and a compact example. The example largely duplicates the schema's own example, which is minor waste but not harmful.

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 correctly compensates by enumerating the returned fields, and it covers both required parameters via the example. Missing only edge-case behavior for unmatched emails, which is a modest gap for a simple two-parameter lookup.

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 both parameters are already documented, including the 'client_id:client_secret' format and paid-plan requirement. The description's inline example call adds a little practical clarity but no semantics beyond the schema, 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 and resource ('look up the person behind an email address') and enumerates the returned fields (name, title, employer, industry, location, social profiles), so the agent knows exactly what it gets. It does not differentiate itself from plausible siblings like entity_profile or company_facts, which keeps it below 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?

Usage is only implied by the enrichment framing; there is no explicit statement of when to prefer this over entity_profile or other lookup tools, and no when-not guidance. An agent can infer it is for email-to-person enrichment, but nothing routes it against alternatives.

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.