Skip to main content
Glama

LinkMCP: hosted LinkedIn MCP server

by io.linkmcp
OverviewDiscussionsAdmin

Search Sales Navigator

linkedin_search_sales_navigator
Read-onlyIdempotent

Search LinkedIn Sales Navigator for people by keywords and filters, or pass a Sales Navigator search URL directly. Returns richer results than classic search including open profile status, premium status, current positions with tenure, and more. Requires a Sales Navigator subscription on the connected LinkedIn account. Text filter values (e.g., "San Francisco" for location) are resolved to LinkedIn IDs automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoSales Navigator search URL (e.g., https://www.linkedin.com/sales/search/people?...). Also accepts classic LinkedIn search URLs. Mutually exclusive with keywords/filters.
cursorNoPagination cursor from a previous response. Pass this to fetch the next page of results.
tenureNoTotal years of work experience (at all companies, not only the current one) as ranges in years (e.g., [{"min": 1, "max": 3}]). Sales Navigator only.
functionNoJob function filter as text values (e.g., ["Engineering", "Finance", "Sales"]). Resolved to LinkedIn department IDs automatically. Sales Navigator only.
industryNoIndustry filter as text values (e.g., ["Software Development"]). Resolved to LinkedIn IDs automatically.
keywordsNoSearch keywords (e.g., "VP engineering"). Required for filter-based search.
locationNoLocation filter as text values (e.g., ["San Francisco Bay Area"]). Resolved to LinkedIn IDs automatically.
seniorityNoSeniority level filter as numeric IDs (1=Unpaid, 2=Training, 3=Entry, 4=Senior, 5=Manager, 6=Director, 7=VP, 8=CXO, 9=Partner, 10=Owner).
network_distanceNoNetwork distance filter (1=1st connections, 2=2nd connections, 3=3rd+).
profile_languageNoProfile language filter as ISO codes (e.g., ["en", "de"]).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tenure / items / properties / max / description
      Previous value: -"Maximum years at current company."New value: +"Maximum total years of work experience."
    • changedInput schema / properties / tenure / items / properties / min / description
      Previous value: -"Minimum years at current company."New value: +"Minimum total years of work experience."
  2. Changed1 schema field changed
    • changedInput schema / properties / tenure / description
      Previous value: -"Tenure at current company filter as ranges in years (e.g., [{\"min\": 1, \"max\": 3}]). Sales Navigator only."New value: +"Total years of work experience (at all companies, not only the current one) as ranges in years (e.g., [{\"min\": 1, \"max\": 3}]). Sales Navigator only."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds genuinely new context: a subscription/auth prerequisite on the connected account, and the automatic resolution of text filter values (e.g. 'San Francisco') to LinkedIn IDs. It does not discuss pagination or rate limits, but that is a minor gap.

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?

Four sentences, front-loaded with the primary action and result benefit, followed by the prerequisite and the auto-resolution note. Each sentence carries information, though the return-field enumeration ('and more') is slightly padded.

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 10-parameter, no-required-param search tool with no output schema, the description covers the two invocation modes, the auth prerequisite, and a sketch of the richer return payload. Pagination via cursor is left entirely to the schema, which is acceptable given the rich parameter descriptions.

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 every parameter is already documented, including the numeric seniority and network_distance encodings and the Sales-Navigator-only markers. The description's mention of URL mode and automatic ID resolution largely restates what the schema descriptions already say, so the baseline 3 is appropriate.

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 ('Search LinkedIn Sales Navigator for people') and explicitly differentiates from the sibling classic search by promising 'richer results than classic search' with named extra fields. An agent can tell it apart from linkedin_search_people without opening either schema.

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?

Gives clear context: two supported modes (keywords+filters, or a Sales Navigator URL), the mutual exclusion of url vs keywords/filters, and the prerequisite of a Sales Navigator subscription. It stops short of an explicit routing rule such as 'use linkedin_search_people when the account has no Sales Navigator seat', so it is clear but not fully exhaustive.

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

All LinkMCP: hosted LinkedIn MCP server 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