campaignstack

Get reviews

campaignstack_get_reviews

Read-onlyIdempotent

Read pending review drafts and optional pending count in one stable envelope. Each item carries what a decision needs: the draft text and the key it sits under, the lead's name, headline, company and profile URL, the channel, the workflow or campaign, the sending account and any flag with its reason. Use include only for extra details the user asked for. Large, computed, historical, or external includes must use their documented caps and must report when data is truncated or paginated. Includes add the lead's full profile, the thread, what the draft answers, the stored draft with its reasoning, and the critic history. Items include kind: workflow for drafted workflow touches and kind: job_application for job watcher cover letters; pass that kind back to campaignstack_decide_review or campaignstack_edit_draft. Use before deciding a review; a page is not the whole queue.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`cursor`	No
`include`	No	Opt-in heavy detail per item. Each item already carries the draft, the lead's name, headline, company and profile URL, and any flag.
`accountId`	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.
`includeCount`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	No
`warnings`	No
`missingIds`	No
`pagination`	No
`pendingCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

addedInput schema / properties / include

Added value: +{
+  "additionalProperties": false,
+  "description": "Opt-in heavy detail per item. Each item already carries the draft, the lead's name, headline, company and profile URL, and any flag.",
+  "properties": {
+    "applicationDetails": {
+      "additionalProperties": false,
+      "description": "Job applications only: every screening answer, the resume file, the apply and posting URLs.",
+      "properties": {},
+      "type": "object"
+    },
+    "context": {
+      "additionalProperties": false,
+      "description": "What the draft answers: the post or comment it reacts to, the shared link and whether it was read, the scheduling-link flag.",
+      "properties": {},
+      "type": "object"
+    },
+    "conversation": {
+      "additionalProperties": false,
+      "description": "The thread so far, oldest first, the newest messages kept.",
+      "properties": {
+        "limit": {
+          "default": 10,
+          "description": "Capped at 50.",
+          "maximum": 50,
+          "minimum": 1,
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "criticHistory": {
+      "additionalProperties": false,
+      "description": "The critic's rank and verdict, and the draft a Retry replaced.",
+      "properties": {},
+      "type": "object"
+    },
+    "draftDetails": {
+      "additionalProperties": false,
+      "description": "The full stored draft output with the model's reasoning and sources.",
+      "properties": {},
+      "type": "object"
+    },
+    "leadProfile": {
+      "additionalProperties": false,
+      "description": "The lead's full profile: about, experiences, education, skills, company facts, LinkedIn profile stats and photo URL.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / limit / default
```
Previous value: -20New value: +10
```

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

AddedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: a 'stable envelope', truncation/pagination reporting, and the requirement that large/computed/historical/external includes respect documented caps. That is real added value beyond structured fields, though it does not explain auth or rate-limit traits.

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 purpose and the decision-relevant item contents, then the include semantics, then the usage directive. It is dense and somewhat long, but nearly every sentence carries new information; the only mild inefficiency is restating the conversation cap that the schema already documents.

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-value explanation is unnecessary. Given six parameters, nested include objects, and two item kinds, the description covers the pagination model, the include/cap contract, the kind routing to sibling tools, and the per-item payload — enough for an agent to invoke correctly without further context.

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 description coverage is only 33%, so the description must compensate, and it does: it enumerates what each include adds (leadProfile, context, conversation, draftDetails, criticHistory, applicationDetails) and what items already carry, letting an agent decide whether an include is needed. limit, cursor, and accountId are left to the schema, which is a minor gap given their simplicity.

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 ('Read pending review drafts and optional pending count') and immediately describes the envelope's contents down to individual item fields. It also names the sibling tools the item kinds feed into (campaignstack_decide_review, campaignstack_edit_draft), so an agent can distinguish it from get_job_applications, recover_review, and get_review_time without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context: 'Use before deciding a review; a page is not the whole queue,' which tells the agent when to call it and warns about pagination completeness. It also scopes the include parameter ('only for extra details the user asked for') and states that kind must be passed back to decide_review/edit_draft. It stops short of naming an explicit alternative for other review-reading needs, so it is not a full when/when-not statement.

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?