Skip to main content
Glama

Decide review

campaignstack_decide_review
Destructive

Approve, reject, or edit-and-approve one pending review. To save a revised draft for a person to sign off instead of deciding it, use campaignstack_edit_draft. For kind workflow, an approved message goes out later, on the account's pacing (business hours, daily budget, spacing between sends), which can take hours; with priority:true it skips the queue and goes out within seconds when the account's send window is open, otherwise at the window's next opening. Use priority only when the user asked for this message to go out now; if campaignstack_get_reviews with this entryId shows a waitReason, tell them why it is waiting. For kind job_application, approval sends or schedules the application within limits; edit_and_approve accepts updatedContent { letter?, answers?: [{ question, answer }] }, and reject may include reason. confirmed:true is required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entryId": "<entryId>",
      "decision": "<decision>",
      "confirmed": "<confirmed>"
    },
    "name": "campaignstack_decide_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoThe item kind from campaignstack_get_reviews. "workflow" (default) is a drafted workflow touch; "job_application" is a job watcher application, where entryId is the application id.
reasonNoJob applications only: why the user rejected the application. Stored on the application.
entryIdYes
decisionYes
priorityNoSend in priority: approve this one message for the current or next account send window, ahead of the queue. It skips the queue's own limits for this message (the daily budget, pacing, the weekly connection cap) and respects business hours and what the account itself says (a paused, expired or risk-paused account refuses it with an error). Set it only when the user asked for this specific message to go out now. Workflow drafts on LinkedIn only; not with reject or job applications.
confirmedYesConfirms the review decision; approve/edit_and_approve can send a real message on the workflow's pacing or submit a job application.
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.
expectedTurnNoFor a conversation reply, the turn campaignstack_get_reviews returned on the item. If the lead wrote again and a newer draft replaced it, the decision is refused so you can read the new one.
updatedContentNo

Output Schema

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / priority / description
      Previous value: -"Send in priority: approve AND send this one message within seconds, instead of waiting its turn in the queue. It skips the queue's own limits for this message (business hours, the daily budget, pacing, the weekly connection cap) but never what the account itself says (a paused, expired or risk-paused account refuses it with an error). Set it only when the user asked for this specific message to go out now. Workflow drafts on LinkedIn only; not with reject or job applications."New value: +"Send in priority: approve this one message for the current or next account send window, ahead of the queue. It skips the queue's own limits for this message (the daily budget, pacing, the weekly connection cap) and respects business hours and what the account itself says (a paused, expired or risk-paused account refuses it with an error). Set it only when the user asked for this specific message to go out now. Workflow drafts on LinkedIn only; not with reject or job applications."
  2. Changed1 schema field changed
    • addedInput schema / properties / expectedTurn
      Added value: +{
      +  "description": "For a conversation reply, the turn campaignstack_get_reviews returned on the item. If the lead wrote again and a newer draft replaced it, the decision is refused so you can read the new one.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / priority
      Added value: +{
      +  "description": "Send in priority: approve AND send this one message within seconds, instead of waiting its turn in the queue. It skips the queue's own limits for this message (business hours, the daily budget, pacing, the weekly connection cap) but never what the account itself says (a paused, expired or risk-paused account refuses it with an error). Set it only when the user asked for this specific message to go out now. Workflow drafts on LinkedIn only; not with reject or job applications.",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"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."
  5. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description goes well beyond them by disclosing real-world consequences: approved workflow messages send on the account's pacing (business hours, daily budget, spacing) and may take hours, priority skips the queue but still respects the send window, and a paused/expired account refuses with an error. The description also notes the confirmed:true requirement and that edit_and_approve submits real content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense paragraph, but it is front-loaded with the action and the routing alternative before the longer behavioral caveats, and every clause carries operational information an agent needs (pacing, priority, per-kind semantics, confirmed requirement). No filler sentences.

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 9-parameter destructive mutation with an output schema already describing returns, the description covers what the schema cannot: side effects, timing, priority trade-offs, and per-kind behavior. Nothing required to call it safely 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 67% schema coverage, the description adds genuine meaning beyond the schema: the workflow vs job_application distinction and how entryId is interpreted per kind, the updatedContent shape { letter?, answers?: [{ question, answer }] }, that reason applies only to rejected job applications, and the operational semantics of priority. It does not explain expectedTurn or workspaceId, which remain schema-only.

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?

The opening sentence gives a specific verb set (approve, reject, edit-and-approve) and a precise resource ('one pending review'), and the second sentence names the sibling campaignstack_edit_draft and the condition that selects it instead. An agent can distinguish this from the draft-editing sibling without reading 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?

It states explicitly when to use priority:true ('only when the user asked for this message to go out now'), when to route to campaignstack_edit_draft, when to consult campaignstack_get_reviews for a waitReason, and which behaviors apply per kind (workflow vs job_application). Exclusions (priority not with reject or job applications) are spelled out.

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