campaignstack

campaignstack_send_inmail

Destructive

Ask CampaignStack to send one InMail to someone the owner is not connected to, from a connected LinkedIn account. Call this when the user has confirmed subject and body for a named person the owner is not connected to; for a connected lead use campaignstack_send_message instead. platform is required ("linkedin"; InMail is a LinkedIn-only premium product and needs Premium, Sales Navigator or Recruiter on the sending account, so a free account has a budget of zero here). Name the person with leadId, which is the supported form; profileUrl is accepted for someone already in the workspace. subject is capped at 200 characters and messageText at 1900. The workspace's only connected LinkedIn account is used automatically, or pass accountId (campaignstack_get_accounts). This reaches a real person. Before calling it, tell the user exactly who it goes to and read the wording back to them, and wait for an explicit yes. It goes out as soon as this call succeeds: there is no draft state and nothing to recall. One person per call. There is no bulk form, and calling this in a loop over a list is not the supported way to reach a list: add the leads with campaignstack_edit_lead_list and run a workflow over it with campaignstack_trigger_workflow, which paces the sends and applies the review step the workspace configured. Sending is paced by CampaignStack's own daily and weekly limits and business hours, which are set by a human in the app and are not writable from here; see overrideOwnLimits before asking for an exception.

Input Schema

TableJSON Schema

Name	Required	Description
`leadId`	No
`subject`	Yes
`platform`	Yes
`accountId`	No
`profileUrl`	No
`messageText`	Yes
`workspaceId`	No	Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.
`overrideOwnLimits`	No	Tells CampaignStack to skip its OWN protective pacing for this one call: the daily budget, the weekly cap, the business-hours window, the account status check and the risk pause. These are limits CampaignStack sets to keep the account healthy. They are not LinkedIn's controls, and nothing here touches, negotiates with or works around anything LinkedIn enforces. LinkedIn's own measured ceiling is a separate check that is never overridable, and neither is a pause the account's owner set. Default false, and it should stay false. Setting it true voids the safety guarantee: from that call on, CampaignStack can no longer promise the pacing that keeps the account out of trouble, and the risk of a restriction sits with the owner. Every use is recorded in the workspace audit log. Ask the owner in plain words and get an explicit yes first. A refusal from the safety system is that system working, not a fault to route around: report the reason and let the person decide, and never retry the same send with this set.
`dangerouslyBypassSafetySystem`	No	Deprecated name for overrideOwnLimits. Use overrideOwnLimits.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobId`	No
`status`	No
`success`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.",
+  "type": "string"
+}

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "jobId": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "success": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed11 schema fields changedSep 14, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / accountId

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / dangerouslyBypassSafetySystem

Added value: +{
+  "description": "Deprecated name for overrideOwnLimits. Use overrideOwnLimits.",
+  "type": "boolean"
+}

addedInput schema / properties / leadId

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / messageText

Added value: +{
+  "maxLength": 1900,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / overrideOwnLimits

Added value: +{
+  "description": "Tells CampaignStack to skip its OWN protective pacing for this one call: the daily budget, the weekly cap, the business-hours window, the account status check and the risk pause. These are limits CampaignStack sets to keep the account healthy. They are not LinkedIn's controls, and nothing here touches, negotiates with or works around anything LinkedIn enforces. LinkedIn's own measured ceiling is a separate check that is never overridable, and neither is a pause the account's owner set. Default false, and it should stay false. Setting it true voids the safety guarantee: from that call on, CampaignStack can no longer promise the pacing that keeps the account out of trouble, and the risk of a restriction sits with the owner. Every use is recorded in the workspace audit log. Ask the owner in plain words and get an explicit yes first. A refusal from the safety system is that system working, not a fault to route around: report the reason and let the person decide, and never retry the same send with this set.",
+  "type": "boolean"
+}

addedInput schema / properties / platform

Added value: +{
+  "enum": [
+    "linkedin"
+  ],
+  "type": "string"
+}

addedInput schema / properties / profileUrl

Added value: +{
+  "format": "uri",
+  "type": "string"
+}

addedInput schema / properties / subject

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "platform",
+  "subject",
+  "messageText"
+]

First observedSep 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, but the description adds substantial extra context the annotations cannot carry: sends immediately with no draft or recall, reaches a real person, requires Premium/Sales Navigator/Recruiter on the sender or the budget is zero, is paced by human-set daily/weekly limits and business hours, and explains what overrideOwnLimits bypasses and that it voids the safety guarantee.

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 action and the alternative are front-loaded, and nearly every sentence carries load (safety, limits, bulk anti-pattern). It is on the long side, and the limits/overrideOwnLimits material could arguably be trimmed since the schema description repeats much of the override explanation.

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?

An output schema exists so return values need not be described. For a high-risk, no-recall send tool with 9 parameters and sparse schema coverage, the description supplies everything needed: recipient identification, confirmation protocol, pacing, and the exception path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, but the description carries the burden: platform is required and LinkedIn-only, leadId is the supported identifier while profileUrl is the fallback, subject caps at 200 and messageText at 1900, accountId is optional with the only connected account used by default, and overrideOwnLimits semantics are spelled out.

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 and resource ('send one InMail to someone the owner is not connected to, from a connected LinkedIn account') and explicitly distinguishes itself from the sibling campaignstack_send_message for connected leads. An agent can route correctly without opening the 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?

Gives explicit when-to-use (user has confirmed subject and body for a non-connected named person), when-not (connected lead → campaignstack_send_message), and the anti-pattern for bulk (looping is unsupported; use campaignstack_edit_lead_list plus campaignstack_trigger_workflow). Alternatives are named with the conditions that select them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All campaignstack tools Inspect

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

Need Help?