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 to its LinkedIn company URL. Returns the LinkedIn URL with a confidence score, plus firmographics such as employee count, industry, and headquarters, and social links, as a flat, Clay-ready JSON row. Provide at least one of company_domain or company_name. 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
With only one tool, there is no risk of ambiguity between tools. The single tool has a distinct and clear purpose.
The single tool name 'resolve_linkedin_url' follows a clear verb_noun pattern, consistent with best practices.
One tool is at the lower end of the range. While it serves a specific resolver function, the surface is minimal and might feel thin for broader use cases.
For the stated purpose of resolving a domain or name to a LinkedIn URL with firmographics, the single tool fully covers the intended operation with no obvious gaps.