LinkedIn Company Page Mapper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| map_linkedin_company_presenceA | Free to run apart from Apify's start fee. Resolve a company domain to its LinkedIn company page, verified against the company's own site, and return the page name and tagline, plus a follower count when public search results show one (2 of 6 test domains on 2026-10-12). No request is sent to LinkedIn: the page comes from the company homepage (structured data or a link) or from a search result whose name matches the name the company site declares or the company_name you pass. A page that cannot be verified is not returned; the row says why in linkedin_verification. The follower count is the search engine's copy and can lag the live page. Industry, size band, headquarters, founded year, specialties and website are no longer returned. 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
Only one tool exists, so there is no risk of selecting between overlapping operations. Its purpose—domain-to-LinkedIn-page mapping—is unmistakable.
The single tool name uses snake_case with a clear verb_noun structure: map_linkedin_company_presence. With only one tool, consistency is trivially satisfied.
A single focused tool is reasonable for this narrow read-only mapping service, but it sits below the typical 3-15 range and offers no batch or alternative operations. Not a mismatch, just slightly thin.
The tool covers the core domain-to-page resolution workflow, including verification and limited follower count. Batch mapping or reverse lookup would round out the surface, but no critical lifecycle operation is missing for a read-only mapper.