Skip to main content
Glama

LinkedIn MCP Server (Salesbot)

by cz.salesbot

create_campaign

Create a NEW campaign (saved as 'draft' — it does NOT start sending until the user activates it in the app). Provide a name, the profile_id to send from, and an ordered list of steps. Each step has an action ('connect', 'message' or 'visit'), an optional delay_hours (wait before this step), and AI/template settings for messages. Returns the new campaign_id. Use add_contacts_to_campaign next to add leads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCampaign name
stepsYesOrdered campaign steps
profile_idYesUUID of the user_profile to send from
daily_limitNoMax actions per day for this campaign. Optional.
descriptionNoOptional description
sender_contextNoContext about the sender used by the AI when writing messages. Optional.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate non-readonly, but description adds crucial behavioral detail: the campaign is created as draft and not automatically active. This goes beyond annotation hints. 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?

Description is concise (3 sentences) and front-loaded with key info: purpose, draft state, required params, step structure, return value, next step. No wasted words.

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?

Covers all essential aspects: creation, draft status, step requirements, return of campaign_id, and a prompt for the next step. Complete for a creation tool lacking output schema.

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 value by explaining step structure, defaults for use_ai and delay_hours, and the purpose of each parameter beyond the schema descriptions.

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 uses a specific verb ('Create'), names the resource ('campaign'), and clarifies it's saved as 'draft'. It distinguishes itself from sibling tools like start_campaign and add_contacts_to_campaign.

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?

Explicitly states the campaign does NOT start sending until activated, and directs to use add_contacts_to_campaign next. Provides clear context for when to use this tool versus alternatives.

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