Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot
OverviewDiscussionsAdmin

search_google_xray

Google X-Ray search for public LinkedIn profiles via Google operators. For company discovery pass the company in keywords and several realistic jobTitles; they are combined with OR in one web query. Existing matching contacts are returned with their contact_id instead of disappearing as duplicates, so they can be enriched. Results remain unverified until enrich_contacts confirms the current employer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (1-100, default 10)
list_idNoUUID of an existing lead list to save the found contacts into (from list_lead_lists). Optional — defaults to the 'Google X-Ray' list.
jobTitleNoOne job title. Use jobTitles for company decision-maker fallback.
keywordsNoAdditional keywords to include in search. Optional.
locationNoLocation filter (e.g. 'Praha', 'Brno'). Optional.
jobTitlesNoAlternative job titles combined with OR in one query, e.g. President, General Manager, Finance Director, Plant Manager.
excludeWordsNoWords to exclude from search. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / jobTitle / description
      Previous value: -"Job title to search for"New value: +"One job title. Use jobTitles for company decision-maker fallback."
    • addedInput schema / properties / jobTitles
      Added value: +{
+  "description": "Alternative job titles combined with OR in one query, e.g. President, General Manager, Finance Director, Plant Manager.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "jobTitle"
-]New value: +[]
  2. Changed1 schema field changed
    • addedInput schema / properties / list_id
      Added value: +{
+  "description": "UUID of an existing lead list to save the found contacts into (from list_lead_lists). Optional — defaults to the 'Google X-Ray' list.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description goes beyond annotations by revealing duplicate handling ('Existing matching contacts are returned with their contact_id instead of disappearing as duplicates'), the OR-combination behavior, and the verification caveat ('Results remain unverified until enrich_contacts confirms the current employer'). Annotations only provide openWorldHint, so this adds substantial behavioral context. No contradiction.

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, front-loaded with the core function, followed by the most actionable usage scenario and the key behavioral caveat. Every sentence contributes unique information and there is no filler.

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 7-parameter search tool with no output schema, the description covers the main scenario, duplicate behavior, and verification status. It doesn't describe the result set shape or pagination, but the schema already documents parameters, and the description gives enough context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter docs are already strong. The description adds cross-parameter meaning by explaining how keywords and jobTitles interact for company discovery ('combined with OR in one web query'). It doesn't need to restate the schema details; the addition is useful.

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?

The description opens with a specific verb+resource: 'Google X-Ray search for public LinkedIn profiles via Google operators.' This clearly distinguishes the mechanism (Google operators) and target (public LinkedIn profiles). It doesn't explicitly contrast with sibling search tools, so it falls short of a 5, but the resource and method are unambiguous.

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?

It gives concrete usage guidance: 'For company discovery pass the company in keywords and several realistic jobTitles; they are combined with OR in one web query.' This is an explicit when/how-to-use instruction. It doesn't state when to prefer a sibling search tool or include exclusions, so not a 5.

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