Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot
OverviewDiscussionsAdmin

search_linkedin_navigator

Run a PEOPLE search from a Sales Navigator or standard LinkedIn search URL and return raw profiles. For company/account URLs use import_linkedin_company_list, which persists a real company list. Sales Navigator URLs require Sales Navigator mode in workspace Settings and an active subscription. URL query filters are preserved. Every provider page is atomically reserved under the matching Salesbot safety preset (Classic max 2 pages/20 profiles; Sales Navigator max 3/30).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10; capped at 20 Classic or 30 Sales Navigator)
cursorNoContinuation cursor returned as remaining_cursor after a partial/deferred page.
search_urlYesFull LinkedIn search URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Continuation cursor returned as remaining_cursor after a partial/deferred page.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (1-100, default 10)"New value: +"Max results (default 10; capped at 20 Classic or 30 Sales Navigator)"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=false (indicating this is not read-only, likely a scraping operation), and the description adds safety limits (Classic max 2 pages/20 profiles; Sales Navigator max 3/30) and atomic reservation under safety presets. This goes beyond generic behavior, though it does not detail data persistence or rate limiting beyond page caps.

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 concise, front-loading the core purpose, then providing exclusions, prerequisites, and safety limits. Every sentence adds value with no redundancy, making it efficient and well-structured.

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 (multiple URL types, safety limits, mode requirements), the description covers key aspects: what it does, when to use alternatives, prerequisites, and limits. It lacks explicit mention of output format, but no output schema exists; however, it does not specify exactly what fields are returned in raw profiles, which could be a minor gap.

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 parameters (limit, cursor, search_url) are all documented in the schema. The description does not add extra semantic detail beyond the schema, but the 'remaining_cursor' mention aligns with schema. Baseline 3 is appropriate as the schema handles parameter documentation.

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 tool performs a PEOPLE search from a Sales Navigator or standard LinkedIn search URL and returns raw profiles. It explicitly differentiates from import_linkedin_company_list for company/account URLs, making the purpose unambiguous and distinct from siblings.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool versus alternatives (e.g., 'For company/account URLs use import_linkedin_company_list'). It also specifies prerequisites (Sales Navigator mode, active subscription) and notes that URL query filters are preserved, giving clear usage context.

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

All LinkedIn MCP Server (Salesbot) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources