campaignstack

Archive job watcher

campaignstack_archive_job_watcher

Destructive

Archive one job watcher permanently. It leaves live watcher lists and never searches or applies again, while previous applications remain readable. Use pause in campaignstack_edit_job_watcher for temporary stops. confirmed:true is required after naming the watcher/account back to the user.

Input Schema

TableJSON Schema

Name	Required	Description
`confirmed`	Yes	Required because archiving is one-way; say the watcher/account back to the user before setting true.
`watcherId`	Yes
`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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`item`	No
`results`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

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

Changed10 schema fields changedSep 26, 2026

addedInput schema / properties / confirmed

Added value: +{
+  "description": "Required because archiving is one-way; say the watcher/account back to the user before setting true.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "workspaceId",
-  "watcherId"
-]New value: +[
+  "watcherId",
+  "confirmed"
+]

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedOutput schema / properties / archived

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": "boolean"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / item
```
Added value: +{}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / results

Added value: +{
+  "items": {},
+  "type": "array"
+}

removedOutput schema / properties / status

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": "string"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / watcherId

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": "string"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / required
```
Added value: +[
+  "ok"
+]
```

AddedSep 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it states the watcher leaves live lists, never searches or applies again, and that previous applications remain readable. That is the exact irreversibility/side-effect profile an agent needs before calling a destructive mutation.

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?

Three sentences, no waste, front-loaded with the permanent/archival nature before the alternative and the confirmation requirement. Every sentence earns its place.

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?

With an output schema present, return values need no explanation, and the description covers irreversibility, the reversible alternative, the confirmation gate, and the workspace resolution is handled by the schema. Nothing needed to call it correctly 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?

Schema coverage is 67%; workspaceId and confirmed are richly documented in the schema, and the description reinforces the confirmed semantics and its user-facing obligation. watcherId remains undocumented in both places, so it falls short of full coverage but adds real meaning for the risky parameter.

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 ('Archive one job watcher permanently') and immediately contrasts with the reversible sibling (pause in campaignstack_edit_job_watcher). An agent can distinguish it from edit_job_watcher 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?

Explicitly names the alternative tool and the condition that selects it: 'Use pause in campaignstack_edit_job_watcher for temporary stops.' It also states the precondition for the destructive path (confirmed:true after naming the watcher/account back to the user).

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?