Skip to main content
Glama

Salesbot - B2B outreach LinkedIn MCP Server with CRM and email

by cz.salesbot
OverviewDiscussionsAdmin

search_linkedin_navigator

Use when you already have a LinkedIn or Sales Navigator search URL. To search by criteria use search_linkedin_people. 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.6/5.0
Behavior5/5

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

Goes well beyond the annotations: Sales Navigator URLs require Sales Navigator mode in workspace Settings plus an active subscription, URL query filters are preserved, and each provider page is atomically reserved under a safety preset with concrete caps (2 pages/20 profiles Classic, 3/30 Sales Navigator). These are auth, rate-limit and side-effect disclosures an agent cannot infer from the schema.

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

Conciseness4/5

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

Front-loads the usage condition and alternative-routing before the operational detail, and no sentence is filler. It is dense with internal jargon ('Salesbot safety preset', 'atomically reserved') and runs to six sentences, which costs a little readability.

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

Completeness5/5

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

No output schema exists, and the description still says what comes back ('raw profiles') and how paging behaves. With auth prerequisites, caps, and sibling alternatives all covered, nothing essential to correct invocation is missing.

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%, so limit, cursor and search_url are already documented, including the cap values and cursor return name. The description adds only marginal semantics ('URL query filters are preserved' for search_url); the baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource ('Run a PEOPLE search ... return raw profiles') and its input mode ('from a Sales Navigator or standard LinkedIn search URL'). It explicitly differentiates from search_linkedin_people and import_linkedin_company_list, so an agent can disambiguate without opening the schema.

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?

Opens with the precise trigger ('Use when you already have a LinkedIn or Sales Navigator search URL') and names the alternative for the opposite case ('To search by criteria use search_linkedin_people'). It also routes company/account URLs to import_linkedin_company_list, giving explicit when/when-not guidance.

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

All Salesbot - B2B outreach LinkedIn MCP Server with CRM and email 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