Skip to main content
Glama

RocketReach (Unofficial)

Rocketreach Find Phone

rocketreach_find_phone
Read-onlyIdempotent

Find a person's phone number via RocketReach, by name + current employer (or linkedin_url / email). Prefers a recommended direct-dial number when more than one is on file. Example: rocketreach_find_phone({ name: "Patrick Collison", current_employer: "Stripe", _apiKey: "your-rocketreach-key" })

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": {
      "name": "Patrick Collison",
      "_apiKey": "your-rocketreach-api-key",
      "current_employer": "Stripe"
    },
    "name": "rocketreach_find_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPerson's full name, e.g. "Patrick Collison". Required together with current_employer unless linkedin_url or email is given.
emailNoOptional known email address, can be used instead of name + current_employer.
_apiKeyNoYour RocketReach API key (generate one on your Account Settings page).
linkedin_urlNoOptional LinkedIn profile URL, can be used instead of name + current_employer.
current_employerNoCompany name the person currently works at, e.g. "Stripe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Optional known email address — can be used instead of name + current_employer."New value: +"Optional known email address, can be used instead of name + current_employer."
    • changedInput schema / properties / linkedin_url / description
      Previous value: -"Optional LinkedIn profile URL — can be used instead of name + current_employer."New value: +"Optional LinkedIn profile URL, can be used instead of name + current_employer."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds a genuinely useful behavioral detail beyond them: it prefers a recommended direct-dial number when multiple numbers exist. It does not disclose credit consumption, no-match behavior, or error modes for an invalid API key, which keeps it below a 5.

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 sentences plus a worked example, with the core action and identifier strategy front-loaded. The example is helpful for a first call but partially redundant with the schema's examples block, which is a minor efficiency loss rather than clutter.

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 single-purpose, read-only lookup with full schema coverage, the description covers what the tool does, how to identify the person, and the output preference. There is no output schema, so a brief statement about the no-match / not-found outcome and per-lookup cost would have closed the remaining gap.

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 the "required together with current_employer unless linkedin_url or email is given" rule, so the baseline is 3. The description restates the same name/employer vs. linkedin_url/email alternatives without adding syntax, formatting, or validation detail beyond the schema; the inline example largely duplicates the schema's examples array.

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?

States a specific verb and resource ("Find a person's phone number via RocketReach") plus the three alternate identification paths. No sibling tool in the catalog performs phone lookup, so there is no ambiguity to resolve, and an agent can tell immediately what this returns.

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?

Implicitly defines the prerequisite inputs (name + current employer, or linkedin_url / email), which tells the agent when the tool is applicable. However, it never says when NOT to use it, what to do if the alternate identifiers are unknown, or how it relates to any other lookup tool — guidance is implied rather than stated.

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.