Skip to main content
Glama

Salesbot - B2B outreach LinkedIn MCP Server with CRM and email

by cz.salesbot
OverviewDiscussionsAdmin

search_crm_leads

Read-onlyIdempotent

Use to find people who are already in the CRM (by name, company, e-mail). To find new people use search_linkedin_people. 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.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false). The description adds useful non-safety context: the searchable fields and the exact identifiers returned. It stops short of describing pagination or sorting behavior, which keeps it from a 5.

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?

The description is front-loaded with the purpose and alternative, then lists search scope and return fields. It is mostly efficient, though the third sentence partially repeats the first and could be trimmed.

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 no output schema, the description usefully enumerates returned identifiers and fields, and with 100% schema coverage the parameters are fully documented. It is nearly complete, missing only minor operational details like pagination and sort behavior already implied by the schema.

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%, so the schema already documents all nine parameters, including enums and defaults. The description reinforces the searchable fields behind 'query' but adds no syntax, format, or interaction details beyond what the schema provides.

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?

The description states a specific verb and resource ('find people who are already in the CRM') and immediately routes to the sibling alternative for new people, so an agent can distinguish it from search_linkedin_people without reading 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool versus the alternative ('To find new people use search_linkedin_people') and adds the key enabling condition that no UUID is needed first, leaving little to inference.

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