Skip to main content
Glama

Edit draft

campaignstack_edit_draft

Save new words on one draft without changing its approval state. Call this when the user asks to revise a draft for someone to sign off later, or to reword a message that is already approved and scheduled. Workflow drafts awaiting review can teach durable writing preferences from the edit immediately. To stop a scheduled draft, use campaignstack_recover_review with mode cancel_scheduled, or reopen for a conversation draft. A draft waiting for review stays waiting (a person still approves it, and the approval is recorded as an edit of the model's draft); a scheduled message keeps its slot; a job application keeps its status and is not approved. It never approves, rejects or sends (campaignstack_decide_review does that).

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>",
      "updatedContent": "<updatedContent>",
      "confirmed": "<confirmed>"
    },
    "name": "campaignstack_edit_draft"
  }
}

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.
entryIdYes
confirmedYesConfirms saving new words on this draft. A scheduled message goes out with them at its slot without another review.
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.
updatedContentYesThe fields to change. For a workflow draft, write the text under the draft.field key campaignstack_get_reviews returned (e.g. { messageText }). For a job application, { letter?, answers?: [{ question, answer }] }.

Output Schema

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare it is a non-idempotent write that is not destructive. The description goes much further: a review-pending draft stays pending with the approval recorded as an edit, a scheduled message keeps its slot and ships without a further review, a job application keeps its status and is not approved, and workflow-draft edits feed durable writing preferences.

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?

The state-preserving guarantee and the when-to-use cases are front-loaded, and every sentence carries a distinct fact. The middle section is dense with parentheticals and repeated state clauses, which costs a little readability without wasted content.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, two-kind mutation with an output schema, it covers the critical ambiguities: approval state is untouched, scheduling is preserved, and side effects differ by kind. Minor gap is that kind-specific content requirements are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 80%, covering kind, entryId, confirmed, workspaceId and updatedContent shapes. The description adds the consequence of confirming a scheduled message but does not otherwise clarify parameter formats beyond what the schema states, so the baseline of 3 applies.

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 first sentence names a specific verb and resource (save new words on one draft) plus a defining constraint (without changing its approval state). It is clearly separable from campaignstack_decide_review and campaignstack_edit_workflow, which the text names or implies.

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 two concrete trigger cases (revise for later sign-off, reword an already-approved and scheduled message) and routes excluded needs elsewhere: cancel via campaignstack_recover_review with mode cancel_scheduled, approve/reject/send via campaignstack_decide_review. Alternatives and boundaries are explicit.

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