Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

campaignstack_comment_on_post

Destructive

Ask CampaignStack to post a comment on a lead's most recent post from a connected LinkedIn account. Call this when the user has approved specific comment wording for a specific lead's post. platform is required (currently "linkedin"). Name the person with leadId, which is the supported form; profileUrl is accepted for someone already in the workspace. commentText must be the owner's own words or wording they approved: draft it with campaignstack_craft_message, or park it for approval with campaignstack_submit_comment_for_review instead of posting it here. The workspace's only connected LinkedIn account is used automatically, or pass accountId (campaignstack_get_accounts). A comment is public and stays under the owner's name. 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
NameRequiredDescriptionDefault
leadIdNo
platformYes
accountIdNo
profileUrlNo
commentTextYes
workspaceIdNoWorkspace 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.
overrideOwnLimitsNoTells 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.
dangerouslyBypassSafetySystemNoDeprecated name for overrideOwnLimits. Use overrideOwnLimits.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdNo
statusNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed10 schema fields changed
    • 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 / commentText
      Added value: +{
+  "maxLength": 1250,
+  "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",
+  "commentText"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds substantial context beyond that: the comment is public and stays under the owner's name, it reaches a real person, there is no draft state and nothing to recall, and sends are paced by workspace-set daily/weekly/business-hours limits that are not writable. It also pre-empts misuse of overrideOwnLimits, describing exactly what it voids and the audit-log consequence.

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?

Front-loaded with the core action and the approval precondition, then routing to alternatives, then safety. It is longer than typical, but nearly every sentence carries routing or safety information. Minor redundancy with the schema's own overrideOwnLimits prose keeps it from a 5.

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 high-risk outbound mutation with an output schema already handling return values, the description covers prerequisites (explicit user yes), targeting, pacing constraints, the one-per-call rule, the bulk workaround, and the override consequences. An agent has everything needed to call it safely and correctly.

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 only 38%, so the description must compensate and does: it explains leadId is the supported form and profileUrl is for existing workspace contacts, that platform is required, that accountId targets a specific connected account, and what commentText must contain. Workspace-level defaults for workspaceId are handled in the schema itself. Some ambiguity remains over exact limit-enforcement interactions, hence not a 5.

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+resource+target: 'post a comment on a lead's most recent post from a connected LinkedIn account.' It distinguishes itself from siblings by naming campaignstack_craft_message, campaignstack_submit_comment_for_review, and the bulk path (campaignstack_edit_lead_list + campaignstack_trigger_workflow), so an agent can tell it apart immediately.

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?

Explicit when-to-use ('when the user has approved specific comment wording'), explicit alternatives for the adjacent cases (draft with craft_message, park for review with submit_comment_for_review), explicit anti-pattern ('calling this in a loop over a list is not the supported way'), and the correct bulk alternative. Nothing is left to inference.

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

All campaignstack 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