Person LinkedIn URL Resolver MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_person_linkedin_urlA | Find a person's LinkedIn profile URL from their name and company domain or company name, read from Google result pages through the Apify Google SERP proxy; LinkedIn itself is never opened. Returns one row per person with linkedin_url, match_status (found at a confidence of 0.8 or more with a clear lead over any other profile, ambiguous with the likely URL, not_found, or blocked), match_confidence from 0 to 1, name_match, company_match (current, former, mentioned, none), the headline, snippet, and follower count Google shows, and the runner up. Batch up to 500 persons in persons. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges one event per person searched (found, ambiguous, or not found); blocked and error rows are free. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap with a sibling. Its purpose is stated precisely (name + company → LinkedIn URL via Google SERP), leaving no ambiguity about what it does or does not do.
The single name resolve_person_linkedin_url follows a clear verb_object convention in snake_case. Nothing else exists to break the pattern, and the name is fully self-describing.
The server's scope is deliberately narrow (one resolution operation), so a single tool is defensible and it absorbs volume via the 500-person batch parameter. Still, a one-tool surface is thin, and the run-ID error path hints at lifecycle operations that were folded into the blob rather than exposed as tools.
The single tool covers the core workflow end to end: batch input, structured output with confidence, match status, matched components, and runner-up, plus explicit blocked/error semantics. The notable gap is that failures return a run ID with no companion tool to retrieve or retry that run, which an agent cannot work around from this surface alone.