Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot

save_lead_message

Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesThe message text.
kindNoWhat this message is, e.g. 'initial' or 'followup' (free text). Default 'initial'.
statusNoLifecycle state. Default 'draft' — set 'sent' after you push it elsewhere.
channelNoWhere this copy is meant to go. Default 'email'.
subjectNoSubject line (for email). Optional.
contact_idYesUUID of the contact (lead).
message_idNoUpdate this existing stored message instead of creating a new one. Optional.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations (readOnlyHint=false, destructiveHint=false) are consistent. Description adds crucial context: the CRM is a 'sponge', no sending occurs, and message_id enables updating drafts. No contradictions.

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 sentences with no wasted words. First sentence explains purpose with examples, second clarifies non-sending and update capability. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no output schema, the description fully covers the workflow (save-then-push), mentions sibling tools for reading and sending, and explains the status lifecycle. No gaps.

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 baseline is 3. Description adds guidance on status field ('set sent after push') and clarifies that message_id updates instead of creates. This extra context raises the score.

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 clearly states the tool stores a generated outreach message on a CRM lead, with specific examples (email, follow-up, LinkedIn). It distinguishes from siblings by explicitly saying it does not send, and mentions updating via message_id.

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?

The description explains when to use: after generating copy, save here. It warns 'Does NOT send anything' and directs to channel-specific tools for sending. It also names complementary read tools (get_lead_context, list_lead_messages).

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap among search tools (search_job_postings, search_google_xray, search_linkedin_people, search_web) and messaging tools (send_connection_request, send_linkedin_message, reply_to_chat). However, detailed descriptions clarify the differences.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., add_contacts_to_campaign, list_campaigns). No mixing of conventions.

Tool Count3/5

48 tools is high but justifiable given the broad domain (LinkedIn outreach, CRM, campaigns, job postings, etc.). However, some tools could be consolidated (e.g., multiple search tools).

Completeness5/5

The tool set covers the entire workflow: searching, connecting, messaging, campaign management, CRM operations (fields, stages, tasks, notes), job postings, and posting. No obvious gaps.

Resources