campaignstack

campaignstack_like_post

Destructive

Ask CampaignStack to like a lead's most recent post from a connected LinkedIn account, as a light way to be seen before writing. Call this when the user asks to like or engage with a specific lead's post before an outreach step. platform is required (currently "linkedin"). Name the person with leadId, which is the supported form; profileUrl is accepted for someone already in the workspace. The workspace's only connected LinkedIn account is used automatically, or pass accountId (campaignstack_get_accounts). A like is public and puts a notification on that person's account under the owner's name. It does not comment; use campaignstack_comment_on_post for that. 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. 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. Business hours do not apply. CampaignStack's daily limit for this action (and the weekly limit for invitations) still applies and counts sends already queued, so a run of calls stops at the limit; the owner sets those limits in the app. A paused account, or an action LinkedIn has challenged, refuses the send whatever the limit.

Input Schema

Name	Required	Description
`leadId`	No
`platform`	Yes
`accountId`	No	Account that acts (LinkedIn account ID). Omit it to default to the workspace's only LinkedIn account that is ready; with several, the error lists them (id and name) so you can ask the person which one.
`profileUrl`	No
`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.
`idempotencyKey`	No	Optional. A key you choose for this one send. Calling again with the same key returns the send already made instead of sending twice (use it when a call timed out); a key reused for a different send is refused. Without a key, the same words to the same person within a few minutes are refused as a repeat.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 14, 2026

addedInput schema / properties / accountId / description

Added value: +"Account that acts (LinkedIn account ID). Omit it to default to the workspace's only LinkedIn account that is ready; with several, the error lists them (id and name) so you can ask the person which one."

removedInput schema / properties / dangerouslyBypassSafetySystem

Removed value: -{
-  "description": "Deprecated name for overrideOwnLimits. Use overrideOwnLimits.",
-  "type": "boolean"
-}

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "Optional. A key you choose for this one send. Calling again with the same key returns the send already made instead of sending twice (use it when a call timed out); a key reused for a different send is refused. Without a key, the same words to the same person within a few minutes are refused as a repeat.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / overrideOwnLimits

Removed 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"
-}

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"
+}

Changed9 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 / 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 / required
```
Added value: +[
+  "platform"
+]
```

First observedSep 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Far exceeds what the annotations convey. It discloses that the like is public and notifies the target under the owner's name, that it reaches a real person, that daily/weekly limits count already-queued sends so a loop stops at the limit, that business hours do not apply, and that paused or LinkedIn-challenged accounts refuse the send. These are exactly the side-effect and failure-mode facts an agent needs for a destructive, open-world write.

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 purpose is front-loaded in sentence one and most sentences carry distinct, load-bearing information (consent, sibling routing, bulk alternative, limits). It is nonetheless a long block, and lines like 'a light way to be seen before writing' and the business-hours aside add length without much decision value.

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 6-parameter, real-world side-effect tool with an output schema, the description covers everything an agent would otherwise have to guess: consent gating, one-person-per-call, account defaulting, no bulk path, and limit/refusal behavior. Return values are the output schema's job and are not redundantly restated.

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 50%, so the description must carry weight, and it does: platform is stated as required (currently only 'linkedin'), leadId is named as the supported identifier while profileUrl is the fallback for someone already in the workspace, and accountId is cross-referenced to campaignstack_get_accounts. The workspaceId and idempotencyKey semantics are left entirely to their schema descriptions, which is the only gap.

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: like a lead's most recent post from a connected LinkedIn account. It immediately distinguishes itself from the nearest sibling by saying it 'does not comment; use campaignstack_comment_on_post for that', so an agent can route correctly without opening 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?

Gives explicit when-to-use (like/engage with a specific lead's post before an outreach step), names the alternative for commenting, and addresses the bulk case by routing to campaignstack_edit_lead_list plus campaignstack_trigger_workflow instead of looping. It also states a required prerequisite (explicit user confirmation before sending).

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?