Skip to main content
Glama

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. 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

NameRequiredDescriptionDefault
leadIdNo
subjectYes
platformYes
accountIdNoAccount 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.
profileUrlNo
messageTextYes
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.
idempotencyKeyNoOptional. 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

NameRequiredDescriptionDefault
jobIdNo
statusNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
      -}
  2. 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"
      +}
  3. 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"
      +}
  4. Changed11 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 / 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"
      +]
  5. 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, but the description adds substantial behavioral context beyond them: it goes out immediately with no draft or recall, Premium/Sales Navigator/Recruiter is required on the sender, business hours do not apply, daily limits count queued sends, and paused or LinkedIn-challenged accounts refuse the send.

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 purpose, then routing, then parameters, then operational warnings, and every sentence carries content. It is long and the limits paragraph could be tightened, but there is little pure filler.

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 destructive, real-world-send mutation with an output schema available for return values, the description covers the confirmation protocol, targeting, account selection, rate limits, idempotency, and anti-patterns; an agent has what it needs to call it safely.

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 largely does: it defines leadId as the supported identifier, profileUrl for someone already in the workspace, platform's LinkedIn-only/premium semantics, and the subject/messageText caps. It does not describe workspaceId or idempotencyKey, which sit in the schema, leaving a small 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 precise verb and resource: 'send one InMail to someone the owner is not connected to, from a connected LinkedIn account.' It immediately contrasts with the sibling campaignstack_send_message for connected leads, so the agent can route 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 ('user has confirmed subject and body for a named person the owner is not connected to'), names the alternative for the adjacent case, and states when-not with the supported bulk path (edit_lead_list + trigger_workflow). 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources