Skip to main content
Glama
gomessoaresemmanuel-cpu

linkedin-prospection-mcp

Find LinkedIn Leads

find_leads

Search LinkedIn for professionals discussing burnout, stress, or exhaustion to identify potential leads for outreach and engagement.

Instructions

Search LinkedIn for leads posting about burnout, stress, or exhaustion. Uses Playwright to scrape LinkedIn posts matching burnout keywords. Requires an active LinkedIn session (run setup-session first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoSimulate without actually scraping

Implementation Reference

  • The handler function for the 'find_leads' tool, which runs the 'find-leads-v2.js' script and processes the results.
      async ({ dry_run }) => {
        if (!fs.existsSync(SESSION_DIR)) {
          return {
            isError: true,
            content: [{ type: "text" as const, text: "LinkedIn session not found. Run setup-session.js first to log in." }],
          };
        }
    
        const args = dry_run ? ["--dry-run"] : [];
        const result = await runScript("find-leads-v2.js", args, 300_000);
    
        if (result.code !== 0) {
          return {
            isError: true,
            content: [{ type: "text" as const, text: `Lead search failed (code ${result.code}):\n${result.stderr}` }],
          };
        }
    
        const leads = getLeads();
        const summary = (leads as { summary?: { p1?: number; p2?: number; p3?: number; total?: number } }).summary;
    
        return {
          content: [
            {
              type: "text" as const,
              text: [
                "Lead search completed!",
                summary ? `P1-hot: ${summary.p1 || 0} | P2-warm: ${summary.p2 || 0} | P3-nurture: ${summary.p3 || 0} | Total: ${summary.total || 0}` : "",
                "",
                result.stdout.slice(-2000),
              ].join("\n"),
            },
          ],
        };
      },
    );
    
    // ─── Tool 2: score_lead ─────────────────────────────────────────
    
    server.registerTool(
      "score_lead",
  • src/index.ts:250-262 (registration)
    Registration of the 'find_leads' tool in the MCP server.
    server.registerTool(
      "find_leads",
      {
        title: "Find LinkedIn Leads",
        description:
          "Search LinkedIn for leads posting about burnout, stress, or exhaustion. " +
          "Uses Playwright to scrape LinkedIn posts matching burnout keywords. " +
          "Requires an active LinkedIn session (run setup-session first).",
        inputSchema: {
          dry_run: z.boolean().default(false).optional().describe("Simulate without actually scraping"),
        },
        annotations: { readOnlyHint: false, openWorldHint: true, destructiveHint: false },
      },
Behavior4/5

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

Annotations indicate external/open-world operation (openWorldHint: true, readOnlyHint: false). Description adds critical implementation context beyond annotations: specifies Playwright for scraping, confirms external data fetching behavior, and discloses authentication requirements not captured in annotations.

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?

Three sentences structured efficiently: purpose (sentence 1), mechanism (sentence 2), prerequisites (sentence 3). No redundancy or filler; every clause provides distinct operational value.

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?

For a single-parameter scraping tool, description adequately covers operational prerequisites (LinkedIn session), implementation method (Playwright), and target data (burnout keywords). Missing output specification, but no output schema exists to require such documentation.

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?

With 100% schema description coverage for the single 'dry_run' parameter ('Simulate without actually scraping'), the schema carries the semantic load. Description does not mention the parameter, but baseline 3 is appropriate given complete schema coverage per rubric guidelines.

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?

Description provides specific verb ('Search'), resource ('LinkedIn posts'), and distinct scope ('burnout, stress, or exhaustion'). Clearly distinguishes from siblings like manage_lead or personalize_message which handle post-discovery actions rather than initial scraping.

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

Usage Guidelines4/5

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

Provides clear prerequisite context ('Requires an active LinkedIn session') implying when-not-to-use. While it doesn't explicitly name alternatives (e.g., 'use manage_lead for existing leads'), the scraping focus and prerequisite guidance provide sufficient contextual guardrails.

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/gomessoaresemmanuel-cpu/linkedin-prospection-mcp'

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