Skip to main content
Glama

Look up someone's contact details

lookupContact

Find the email and phone number for a person, from their LinkedIn profile URL.

This runs asynchronously. It returns immediately with status "pending" and a lookupId. You MUST then call checkContactLookup with that lookupId to get the result. Wait roughly 30 seconds before the first check. Do not tell the user you have their details until a check comes back "completed".

Costs one of 25 lookups per day for the company, and every call counts, including repeats of the same person.

If the URL belongs to someone in Clera's network, this always refuses and points you at requestIntro instead: Clera never hands out a candidate's email or phone, and they hear it from Clera first, which converts far better than a cold email.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "linkedin_url": "<linkedin_url>"
    },
    "name": "lookupContact"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
linkedin_urlYesFull LinkedIn profile URL, e.g. https://www.linkedin.com/in/some-handle

Output Schema

NameRequiredDescriptionDefault
emailYes
phoneYes
statusYes
fullNameYes
lookupIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false; the description adds far more: asynchronous pending/lookupId lifecycle, quota consumption per call including duplicates, a hard refusal condition for network contacts, and a data-recording disclosure. None of this contradicts the annotations — non-idempotent and non-read-only are consistent with a quota-consuming, network-dependent lookup.

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?

Purpose is front-loaded and the following paragraphs each carry distinct load: async protocol, cost, refusal/alternative, privacy. It is on the long side with five short blocks, and the privacy sentence is boilerplate, but nothing is genuinely redundant or misleading.

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?

An output schema exists, so return-value detail is unnecessary; the description instead covers the one thing an agent must know that the schema cannot express — that a 'pending' response is not a result. Quota, refusal behavior, and privacy disclosure round out a complete picture for a two-parameter async tool.

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% and both parameters are already documented, including the URL format example and the multi-org caveat for orgId. The description reinforces that the URL must be a LinkedIn profile but adds no new semantics such as accepted URL variants or what happens with a malformed URL. Baseline 3 is appropriate.

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?

Opens with a specific verb and resource ('Find the email and phone number for a person') plus the exact input it derives from ('from their LinkedIn profile URL'). This is clearly distinguishable from checkContactLookup (which retrieves results) and requestIntro (which is the alternative path).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit follow-up instructions (call checkContactLookup with the lookupId, wait ~30 seconds, don't report success until status is 'completed'), an explicit exclusion that redirects to requestIntro when the person is in Clera's network, and a budget rule (25/day, repeats count). When-to-use, when-not-to-use, and the alternative are all named.

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.

Resources