Skip to main content
Glama
freesolo-co

Clado MCP Server

by freesolo-co

scrape_linkedin

Extract detailed LinkedIn profile data and posts with comments from any profile URL to gather professional insights and content analysis.

Instructions

Retrieves detailed profile data and posts with comments from a LinkedIn profile URL using RapidAPI. Each request costs 2 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkedin_urlYesThe LinkedIn profile URL to scrape.

Implementation Reference

  • The main handler function that implements the 'scrape_linkedin' tool. It takes a LinkedIn URL, makes a request to the Clado API for scraping, handles errors, and returns the scraped data formatted as tool content.
    export const scrapeLinkedinTool = async ({
      linkedin_url,
    }: ScrapeLinkedinParams) => {
      const apiUrl = new URL("https://search.clado.ai/api/enrich/scrape");
      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 scrape LinkedIn profile: ${JSON.stringify(responseData.error)}`
        );
      }
    
      return {
        content: [
          {
            type: "text" as const,
            text: `profile scraping completed successfully: ${JSON.stringify(responseData, null, 2)}`
          }
        ]
      };
    };
  • The Zod-based input schema defining the 'linkedin_url' parameter for the tool.
    export const scrapeLinkedinSchema = {
      linkedin_url: z.string().describe("The LinkedIn profile URL to scrape."),
    };
  • src/index.ts:45-50 (registration)
    Registration of the 'scrape_linkedin' tool on the MCP server in the main index file.
    server.tool(
      scrapeLinkedinName,
      scrapeLinkedinDescription,
      scrapeLinkedinSchema,
      scrapeLinkedinTool
    );
  • Registration of the 'scrape_linkedin' tool on the MCP server in the server setup utility.
    server.tool(
      scrapeLinkedinName,
      scrapeLinkedinDescription,
      scrapeLinkedinSchema,
      scrapeLinkedinTool
    );
Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses the cost per request ('2 credits'), which is a rate-limiting consideration not evident from the schema. However, it does not mention authentication requirements, rate limits beyond cost, or error handling.

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 and front-loaded: the first sentence states the core purpose and scope, and the second adds critical cost information. Both sentences earn their place with no wasted words or redundancy.

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

Completeness3/5

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

Given the tool's complexity (data scraping with cost implications), no annotations, and no output schema, the description is minimally adequate. It covers purpose and cost but lacks details on output structure, error cases, or prerequisites like API keys, leaving gaps for the agent to handle.

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?

Schema description coverage is 100%, so the schema already documents the 'linkedin_url' parameter fully. The description does not add any parameter-specific details beyond what the schema provides, such as URL format examples or validation rules, meeting the baseline for high schema coverage.

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 data and posts with comments') and resource ('from a LinkedIn profile URL'), distinguishing it from siblings like 'enrich_linkedin' or 'linkedin_post_reactions' by specifying the comprehensive data retrieval scope.

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 context by mentioning the data source ('LinkedIn profile URL') and API provider ('RapidAPI'), but does not explicitly state when to use this tool versus alternatives like 'enrich_linkedin' or 'search_for_users', leaving the agent to infer based on the data types mentioned.

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/mcp'

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