Skip to main content
Glama
Sign In

Salesbot - B2B outreach LinkedIn MCP Server with CRM and email

by cz.salesbot
OverviewDiscussionsAdmin

create_campaign

Create a NEW campaign (saved as 'draft' — it does NOT start sending until the user activates it in the app). BEFORE calling, ask the user which campaign type they want unless they already said it — never choose it yourself: 1. Outreach with 2 messages: visit → connect (48 h) → message 1 (24 h) → message 2 (7 days) 2. Outreach with 1 message: visit → connect (24-48 h) → message 1 (48 h) 3. Nurturing – 3 messages: visit → connect (24-48 h) → messages after 24 h, 5 days, 7 days 4. Connection only: visit → connect (12-48 h), no messages 5. Existing connections – 3 messages: messages now, after 5 days, after 7 days (1st-degree connections only) 6. One-off message to existing connections: one message (1st-degree connections only). Confirm the planned steps with the user first. 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.

MESSAGE PLACEHOLDERS (for ai_template / when use_ai is false, also cleaned up after AI):

  • {oslovení} or [Oslovení]/[Jméno] → Czech vocative greeting (e.g. 'pane Nováku' / first-name vocative like 'Petře')

  • {{first_name}} or {jméno}/{jmeno} or [Name]/[first_name] → contact first name

  • {{company}} or {firma} or [Firma]/[Company] → company name ({firma} = sender company from sender_context; {{company}}/[Firma] = lead's company)

  • {{jmeno_5p}} → Czech first-name vocative ('Petře'); {{prijmeni_5p}} → Czech surname vocative without 'pane' ('Kubíčku', women unchanged)

  • Language: when the sample/prompt is English (or the prompt says 'in English'), Czech salutation rules are off and all name variables give plain names ('Hi Petr,')

  • Also: {{last_name}}, {{full_name}}, {{position}}, {{location}}, {{headline}}

  • {{company_info}} → one-sentence description of what the lead's company does. Optional: it exists only if you saved it with update_contact (company_info, e.g. from read_company_website); if missing, it falls back to the generic "ve firmě". Never invent it. Prefer {{first_name}} / {{company}} / {oslovení} in new templates; square brackets like [Jméno] and [Firma] are supported aliases.

Input 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.
message_languageNoLanguage of the messages. 'cs' = Czech salutation ("Dobrý den, pane Kubíčku,"), 'en' = English ("Hi Petr," / "Dear Mr. Kubíček,"), 'pl' = Polish ("Dzień dobry, Panie Piotrze,"). Ask the user when unclear; omitted = decided from the sample message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / message_language / description
      Previous value: -"Language of the messages. 'cs' = Czech salutation (\"Dobrý den, pane Kubíčku,\"), 'en' = English (\"Hi Petr,\" / \"Dear Mr. Kubíček,\"). Ask the user when unclear; omitted = decided from the sample message."New value: +"Language of the messages. 'cs' = Czech salutation (\"Dobrý den, pane Kubíčku,\"), 'en' = English (\"Hi Petr,\" / \"Dear Mr. Kubíček,\"), 'pl' = Polish (\"Dzień dobry, Panie Piotrze,\"). Ask the user when unclear; omitted = decided from the sample message."
    • changedInput schema / properties / message_language / enum
      Previous value: -[
-  "cs",
-  "en"
-]New value: +[
+  "cs",
+  "en",
+  "pl"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / message_language
      Added value: +{
+  "description": "Language of the messages. 'cs' = Czech salutation (\"Dobrý den, pane Kubíčku,\"), 'en' = English (\"Hi Petr,\" / \"Dear Mr. Kubíček,\"). Ask the user when unclear; omitted = decided from the sample message.",
+  "enum": [
+    "cs",
+    "en"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / steps / items / properties / ai_prompt / description
      Previous value: -"Instructions for the AI message"New value: +"Instructions for the AI message. The campaign's sender_context (\"About me\") is NOT added automatically — write {{o_mne}} in the prompt where the AI should use it. Links written in the prompt or ai_template are kept exactly, in the place where they are written."
  4. Changed2 schema fields changed
    • changedInput schema / properties / steps / items / properties / ai_template / description
      Previous value: -"Template / style sample. Placeholders: {oslovení}, {{first_name}}, {jméno}, {{company}}, {firma}, [Jméno], [Firma], etc. When use_ai is false (or AI falls back), placeholders are replaced automatically."New value: +"Sample message. Placeholders: {oslovení}, {{first_name}}, {jméno}, {{company}}, {firma}, [Jméno], [Firma], etc. When use_ai is false (or AI falls back), placeholders are replaced automatically. How it is used depends on message_mode."
    • addedInput schema / properties / steps / items / properties / message_mode
      Added value: +{
+  "description": "'template' = ai_template IS the message: sent word for word, the AI only fills its fields (e.g. [Firma] → \"Škoda Auto\" per the ai_prompt). 'creative' = the AI writes a new message per lead from ai_prompt and uses ai_template only as a style example. Default: 'creative' when both ai_prompt and ai_template are given, otherwise 'template'.",
+  "enum": [
+    "template",
+    "creative"
+  ],
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedInput schema / properties / steps / items / properties / ai_template / description
      Previous value: -"Fallback / non-AI template text"New value: +"Template / style sample. Placeholders: {oslovení}, {{first_name}}, {jméno}, {{company}}, {firma}, [Jméno], [Firma], etc. When use_ai is false (or AI falls back), placeholders are replaced automatically."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, but the description adds the crucial behavioral fact that the campaign is created as a draft and does not send until user activation — something not derivable from structured fields. It also states the return value (new campaign_id).

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?

Core creation rules, the type enumeration, and the confirmation requirement are front-loaded before the placeholder glossary. It is long, but the length is justified by the templating complexity; the placeholder block is dense and partly duplicates schema text, costing it a point.

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 nested-step creation tool with no output schema, the description covers draft semantics, required fields, step ordering, templating behavior, message language, and the next tool to call. Nothing essential for correct invocation is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds genuine meaning: it names the three required inputs, requires steps to be an ordered list with an action and optional delay_hours, and provides a placeholder convention glossary ({oslovení}, {{first_name}}, {firma} vs {{company}}) that is not fully captured in the schema.

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?

Opens with a specific verb+resource ('Create a NEW campaign') and immediately clarifies the resulting state (saved as 'draft', will not send until activated). It also explicitly routes to the sibling add_contacts_to_campaign, so the agent can distinguish it from start_campaign and update_campaign_settings.

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 gives explicit preconditions (ask the user which of six campaign types, never choose yourself; confirm planned steps first) and names the follow-up tool. This is the rare case of clear when/when-not/next-step guidance.

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