mcp-domain-to-linkedin-url-resolver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token |
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_linkedin_urlA | Resolve a company domain or name, or a list of domains, to the LinkedIn company URL. Returns one flat, Clay-ready JSON row per company with the LinkedIn URL and slug, a confidence of high, medium, or low, the resolution method, and Facebook, Instagram, X, and YouTube links. The URL is read from public search results; no request is ever sent to LinkedIn. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets only when includeFirmographics is true; with it off, or when no snippet states them, those fields are null. Successful resolutions are cached for 7 days unless skipCache is true. Use it when you have a domain or a name and need the LinkedIn company page; it does not find people. Provide company_domain, company_name, or domains. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call. |
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 confusing it with a sibling tool. Its purpose (domain/name to LinkedIn company URL) is stated explicitly, including what it does not do (find people).
The single name resolve_linkedin_url follows a clear snake_case verb_noun convention. There are no competing conventions to clash with.
One tool is thin in absolute terms, but the server's scope is intentionally narrow and the tool absorbs single/batch input, firmographics, caching, and multi-platform social output. It is slightly under-scoped rather than mismatched, since there is no second operation (e.g. reverse lookup, cache management) exposed.
For a domain-to-LinkedIn-URL resolver, the surface covers the core operation plus batch input, optional firmographics, confidence scoring, and error/run-ID reporting. Minor gaps exist (no reverse LinkedIn-to-domain lookup, no cache inspection/clearing), but nothing that blocks the primary workflow.