ZOOQ - LinkedIn Data for AI Agents

email_find_by_profile

Read-onlyIdempotent

Identify a person and their current company from a professional profile URL (or handle), then find their work email — resolves name + domain for you. (Costs 10 Zooq credits.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "email_find_by_profile"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	A professional profile URL or its bare public handle.

Output Schema

Name	Required	Description
`url`	No	Example value was a string
`email`	No	Example value was a string
`found`	No	Example value was a boolean
`domain`	No	Example value was a string
`company`	No	Example value was a string
`catch_all`	No	Example value was a boolean
`last_name`	No	Example value was a string
`confidence`	No	Example value was a string
`first_name`	No	Example value was a string

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the 10-credit cost and by stating that it 'resolves name + domain for you,' which sets expectations for enrichment behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler: the first states the core function and input, the second discloses the cost. The main behavior is front-loaded, and every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, idempotent lookup with a single parameter and an output schema, the description covers all invocation-critical details: input form, resolution behavior, and cost. The output schema handles return-value documentation, so nothing an agent needs to call it correctly is missing.

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%; the parameter description 'A professional profile URL or its bare public handle' fully defines the accepted input forms. The main description repeats this without adding new syntactic or format details. Baseline 3 is appropriate because the schema carries the semantic weight.

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 and resource: 'Identify a person and their current company from a professional profile URL (or handle), then find their work email.' This clearly distinguishes it from siblings like email_find (likely input is email) and email_verify (verify existing email) by specifying the input is a profile URL or handle. The title 'Find email from LinkedIn profile' reinforces the purpose.

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?

The intended usage is explicit: provide a professional profile URL or bare handle, and the tool resolves name + domain then finds work email. There is no explicit 'when not to use' or alternative routing, but the input condition is so clearly stated that an agent can infer when this is the appropriate tool among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ZOOQ - LinkedIn Data for AI Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.