Skip to main content
Glama

Salesbot - B2B outreach LinkedIn MCP Server with CRM and email

by cz.salesbot
OverviewDiscussionsAdmin

search_google_xray

Fallback people search through Google, e.g. when search_linkedin_people is protected or times out. Not for general web research (use search_web). 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.5/5.0
Behavior4/5

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

Adds real value beyond the annotations: it explains that matching contacts are returned with their contact_id rather than being silently deduped, that results are saved into a list, and that output stays unverified until enrich_contacts runs. This discloses write/persistence and verification lifecycle behavior the annotations don't cover, though it doesn't detail rate limits or failure modes.

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 purpose and fallback trigger, then layers usage and behavioral notes. Dense but each sentence carries information; the two 'Google X-Ray' references are slightly redundant but not wasteful.

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?

With seven optional params, no output schema, and non-read-only annotations, the description covers the important gaps: what happens to existing matches, where results land, and their unverified state. Return-shape details are deferred to enrich_contacts, which is reasonable.

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 the baseline is 3, but the description adds semantics the schema lacks: jobTitles are combined with OR in one query, and for company discovery you pass the company in keywords plus several jobTitles. It also clarifies the jobTitle vs jobTitles distinction contextually.

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 ('people search through Google' / 'Google X-Ray search for public LinkedIn profiles') and explicitly positions itself against siblings by name. An agent can tell it apart from search_linkedin_people and search_web without opening any 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?

Gives an explicit invocation trigger ('when search_linkedin_people is protected or times out'), a clear exclusion ('Not for general web research (use search_web)'), and even a use pattern for company discovery. Alternatives and conditions are stated directly.

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