Skip to main content
Glama
freesolo-co

Clado MCP Server

by freesolo-co

enrich_linkedin

Retrieve detailed LinkedIn profile information from a URL to enrich contact data and support research activities.

Instructions

Retrieves detailed profile information for a specific LinkedIn URL. Each successful lookup costs 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedin_urlYesThe LinkedIn profile URL to look up.

Implementation Reference

  • The main handler function `enrichLinkedinTool` that executes the tool logic: constructs API URL, calls `makeCladoRequest` to enrich the LinkedIn profile, handles errors, and returns formatted response.
    export const enrichLinkedinTool = async ({
      linkedin_url,
    }: EnrichLinkedinParams) => {
      const apiUrl = new URL("https://search.clado.ai/api/enrich/linkedin");
      apiUrl.searchParams.append("linkedin_url", linkedin_url);
    
      const response = await makeCladoRequest(apiUrl.toString(), {});
      const responseData = await response.json();
    
      if (responseData.error) {
        throw new Error(
          `Failed to enrich LinkedIn profile: ${JSON.stringify(responseData.error)}`
        );
      }
    
      return {
        content: [
          {
            type: "text" as const,
            text: `enrichment completed successfully: ${JSON.stringify(responseData, null, 2)}`
          }
        ]
      };
    };
  • Zod schema defining the input parameter `linkedin_url` for the tool.
    export const enrichLinkedinSchema = {
      linkedin_url: z.string().describe("The LinkedIn profile URL to look up."),
    };
  • src/index.ts:32-36 (registration)
    Registration of the `enrich_linkedin` tool on the MCP server in the main index file.
      enrichLinkedinName,
      enrichLinkedinDescription,
      enrichLinkedinSchema,
      enrichLinkedinTool
    );
  • Registration of the `enrich_linkedin` tool on the MCP server in the server setup utility.
      enrichLinkedinName,
      enrichLinkedinDescription,
      enrichLinkedinSchema,
      enrichLinkedinTool
    );
  • Tool name constant used for registration.
    export const enrichLinkedinName = "enrich_linkedin";
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds value beyond the input schema by stating 'Each successful lookup costs 1 credit,' which is crucial context about cost implications. However, it doesn't cover other behavioral traits like rate limits, error handling, or response format, leaving some gaps in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with two sentences: the first states the purpose, and the second adds critical behavioral context (cost). It's front-loaded with the core functionality and avoids unnecessary details, making every sentence earn its place without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a single-parameter lookup with cost implications) and no annotations or output schema, the description is fairly complete. It covers the purpose and cost, but lacks details on output format or error cases. For a tool with no structured output documentation, it could be more comprehensive, but it provides enough context for basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'linkedin_url' clearly documented. The description doesn't add any additional meaning beyond what the schema provides (e.g., it doesn't specify URL format or validation rules). According to the rules, with high schema coverage, the baseline is 3, and the description doesn't compensate further, so this score is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Retrieves detailed profile information') and resource ('for a specific LinkedIn URL'), distinguishing it from sibling tools like 'linkedin_post_reactions' (which deals with reactions) and 'scrape_linkedin' (which might be more general). It precisely communicates what the tool does without being vague or tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning 'for a specific LinkedIn URL,' suggesting it's for individual profile lookups, but it doesn't explicitly state when to use this tool versus alternatives like 'search_for_users' (which might search by name) or 'retrieve_contacts' (which might handle bulk data). There's no guidance on exclusions or prerequisites, leaving usage context somewhat inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freesolo-co/search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server