Skip to main content
Glama
gomessoaresemmanuel-cpu

linkedin-prospection-mcp

Manage Lead Status

manage_lead

Update lead status and add notes in the LinkedIn prospection pipeline to track engagement progress.

Instructions

Update a lead's status in the pipeline. Use this to mark leads as contacted, replied, not_interested, or to add notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesLead name (partial match supported)
statusYesNew status
notesNoOptional notes about the lead

Implementation Reference

  • The `manage_lead` tool registration and handler implementation. It updates a lead's status and notes in the daily prospection log.
    server.registerTool(
      "manage_lead",
      {
        title: "Manage Lead Status",
        description:
          "Update a lead's status in the pipeline. Use this to mark leads as contacted, " +
          "replied, not_interested, or to add notes.",
        inputSchema: {
          name: z.string().describe("Lead name (partial match supported)"),
          status: z.enum([
            "pending_invitation", "invitation_sent", "connection_accepted",
            "dm_sent", "replied", "meeting_booked", "not_interested", "removed",
          ]).describe("New status"),
          notes: z.string().optional().describe("Optional notes about the lead"),
        },
        annotations: { readOnlyHint: false, openWorldHint: false, destructiveHint: false },
      },
      async ({ name, status, notes }) => {
        const logPath = getDailyLogPath();
        const log = getDailyLog() as {
          leads_p1?: Array<Record<string, unknown>>;
          leads_p2?: Array<Record<string, unknown>>;
        };
    
        const nameLower = name.toLowerCase();
        let found = false;
        let matchedName = "";
    
        for (const pool of [log.leads_p1 || [], log.leads_p2 || []]) {
          for (const lead of pool) {
            if ((lead.name as string || "").toLowerCase().includes(nameLower)) {
              lead.status = status;
              if (notes) lead.notes = notes;
              lead.updated_at = new Date().toISOString();
              found = true;
              matchedName = lead.name as string;
              break;
            }
          }
          if (found) break;
        }
    
        if (!found) {
          return {
            isError: true,
            content: [{ type: "text" as const, text: `Lead "${name}" not found in pipeline.` }],
          };
        }
    
        fs.writeFileSync(logPath, JSON.stringify(log, null, 2));
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Updated ${matchedName} → status: ${status}${notes ? ` | notes: ${notes}` : ""}`,
            },
          ],
        };
      },
    );
Behavior3/5

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

Annotations already indicate this is a non-destructive write operation (readOnlyHint: false, destructiveHint: false). The description adds domain context ('pipeline') and maps the tool to specific business actions. However, it omits error handling (what happens if name doesn't match?), idempotency, or side effects like notifications triggered.

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?

Two efficient sentences with zero waste. Front-loaded with the core action ('Update a lead's status'), followed immediately by usage examples. Every word earns its place.

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?

Appropriate for a 3-parameter tool with 100% schema coverage and annotations present. The description adequately covers the tool's function without needing to explain return values (no output schema). Could improve by mentioning the partial match behavior on 'name' or workflow integration with find_leads.

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 coverage is 100%, providing the baseline. The description reinforces the semantics by mapping the tool to concrete use cases (marking as contacted, adding notes), which helps the agent understand the business logic behind the 'status' enum and 'notes' field, though it doesn't add syntactic details beyond the schema.

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

Purpose4/5

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

Clear specific verb ('Update') and resource ('lead's status in the pipeline'). Lists concrete status examples (contacted, replied, not_interested). Deducted one point because it doesn't explicitly distinguish from siblings like 'qualify_leads' or 'score_lead' which might also modify lead data, though the status focus is distinct.

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?

Provides usage examples ('Use this to mark leads as...') implying when to use it, but lacks explicit guidance on prerequisites (e.g., using find_leads first to locate the lead) or when NOT to use it vs. alternatives like 'run_pipeline' (likely for bulk operations) or 'qualify_leads'.

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