Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot
OverviewDiscussionsAdmin

search_crm_leads

Read-onlyIdempotent

Search and filter CRM leads across all contact lists without knowing a UUID first. Searches name, company, email, role, headline, LinkedIn URL and campaign name. Returns contact_id, crm_lead_id, crm_company_id, list_id, campaign_id, pipeline stage, deal value and timestamps for the next CRM or campaign action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum rows (default 50, max 200).
queryNoOptional text search across name, company, email, role, headline, LinkedIn URL and campaign name.
stageNoOptional pipeline stage key, e.g. demo or won.
offsetNoPagination offset (default 0).
list_idNoOptional contact-list UUID filter.
sort_byNoSort field. Default updated_at.
campaign_idNoOptional campaign UUID filter.
crm_company_idNoOptional CRM company UUID filter (people at one account).
sort_directionNoSort direction. Default desc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / crm_company_id
      Added value: +{
+  "description": "Optional CRM company UUID filter (people at one account).",
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable behavioral context: it searches across all lists, lists return fields, and mentions timestamps for next actions, enriching beyond structured annotations.

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?

Two focused sentences: the first front-loads the key differentiator (no UUID needed) and scope, the second lists searchable fields and return fields. Zero redundancy, 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 no output schema, the description lists return fields, which is essential. It also states search scope and fields. It omits explicit mention of pagination or sort defaults, but those are documented in the schema, so the description is adequately complete for a search tool.

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% with meaningful descriptions for all 9 parameters. The description adds only marginal context (e.g., default search across all lists) but does not explain parameter syntax or interactions beyond the schema, which already handles the 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 'Search and filter', resource 'CRM leads', and a differentiating scope 'across all contact lists without knowing a UUID first'. Lists exact searchable fields and return fields, making its function unmistakable and distinct from sibling tools like get_contact_profile that require UUIDs.

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?

Clearly implies usage when a UUID is unknown and emphasizes broad cross-list search, which guides selection. However, it does not explicitly name alternatives or state when not to use it, leaving some inference to the agent.

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