Skip to main content
Glama

Recover review

campaignstack_recover_review

Recover one review with mode retry, restore_superseded_draft, reopen, or cancel_scheduled. To stop an approved scheduled workflow draft before sender handoff, use mode cancel_scheduled to cancel one draft, or mode reopen for a conversation draft: it returns the same text to pending review and releases its slot. Then decide_review reject can discard it. Once handed to the sender, both modes return an error. Retry may spend a fresh model generation; reopen validates downstream safety.

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>",
      "mode": "<mode>",
      "confirmed": "<confirmed>"
    },
    "name": "campaignstack_recover_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
entryIdYes
confirmedYesConfirms recovering or cancelling this draft. Retry may spend a fresh model generation.
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.

Output Schema

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / confirmed / description
      Previous value: -"This can spend credits, paid provider quota, or model-backed work. Tell the user the cost or budget meaning first when the tool reports one."New value: +"Confirms recovering or cancelling this draft. Retry may spend a fresh model generation."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "retry",
      -  "restore_superseded_draft",
      -  "reopen"
      -]New value: +[
      +  "retry",
      +  "restore_superseded_draft",
      +  "reopen",
      +  "cancel_scheduled"
      +]
  2. 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."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it is a non-readonly, non-idempotent mutation, but the description adds real context beyond them: retry may consume a fresh model generation, reopen validates downstream safety, both modes error after sender handoff, and the draft's slot is released. These are exactly the side effects an agent needs before calling. No claim conflicts with the annotations.

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?

Four sentences, purpose front-loaded, no filler. The 'Then decide_review reject can discard it' sentence is slightly compressed and its referent ('it' = the reopened draft) takes a re-read, but overall the density is warranted for a four-mode tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be explained, and the pre/post-handoff behavior is well covered. However, for a tool whose whole interface is the mode enum, leaving restore_superseded_draft entirely undefined is a substantive gap — the agent must guess what that mode recovers.

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?

The schema covers only 50% of parameters, so the description must carry weight — and it does for the most important one, explaining what each of the four mode enum values actually does behaviorally. entryId receives no explanation in either the schema or the description, which is the main remaining gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Recover one review') and enumerates the four supported modes, so an agent can distinguish it from campaignstack_decide_review. It is slightly muddied by lumping 'cancel_scheduled' under the verb 'recover', but the resource and mode set are unambiguous.

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?

It gives a concrete decision rule — use cancel_scheduled to stop an approved scheduled workflow draft before sender handoff, or reopen for a conversation draft — and points to decide_review reject as the follow-on discard path. It also states the hard boundary (error once handed to the sender). What is missing is guidance on when to pick retry versus restore_superseded_draft.

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