Clado MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLADO_API_KEY | Yes | Your Clado API key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_for_usersC | Search for users on Clado using filters like query, school, and match threshold. |
| enrich_linkedinA | Retrieves detailed profile information for a specific LinkedIn URL. Each successful lookup costs 1 credit. |
| retrieve_contactsA | Retrieves email addresses and phone numbers for LinkedIn profiles. Supports reverse lookup via email or phone. Email enrichment costs 4 credits if found, phone enrichment costs 10 credits if found. |
| scrape_linkedinA | Retrieves detailed profile data and posts with comments from a LinkedIn profile URL using RapidAPI. Each request costs 2 credits. |
| linkedin_post_reactionsC | Retrieves reactions and engagement data for a specific LinkedIn post URL. |
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 5 tools
The tools have some overlap in purpose, particularly between 'enrich_linkedin' and 'scrape_linkedin', which both retrieve LinkedIn profile data, though 'scrape_linkedin' includes posts and comments. 'retrieve_contacts' focuses on contact information, while 'linkedin_post_reactions' and 'search_for_users' are more distinct. Descriptions help differentiate them, but confusion could arise between the profile-focused tools.
Most tools follow a consistent verb_noun pattern (e.g., 'enrich_linkedin', 'scrape_linkedin', 'search_for_users'), which is clear and predictable. However, 'retrieve_contacts' uses 'retrieve' instead of a more aligned verb like 'get' or 'enrich', causing a minor deviation. Overall, the naming is mostly consistent and readable.
With 5 tools, the count is well-scoped for a LinkedIn-focused server, covering key operations like profile enrichment, contact retrieval, post analysis, and user search. Each tool appears to serve a distinct purpose, and the number is neither too sparse nor overwhelming for the domain.
The tool set covers core LinkedIn data retrieval functions, including profile enrichment, contact information, post engagement, and user search. Minor gaps exist, such as the lack of tools for updating or managing data (e.g., no 'create_contact' or 'delete_profile'), but agents can likely work around these for typical lookup and analysis tasks.