Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

campaignstack_delete_signal_watch

Destructive

Delete person signal watches by archiving them so they no longer refresh. Call this only after the user confirms the exact watches to remove. This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes. Batch edits are bounded. Return one result per requested item, and report partial failures instead of describing the whole batch as successful.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
watchIdsYes
confirmedYesThis permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.
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

TableJSON Schema
NameRequiredDescriptionDefault
resultsNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / confirmDelete
      Removed value: -{
-  "const": true,
-  "description": "This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmed
      Added value: +{
+  "const": true,
+  "description": "This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "watchIds",
-  "confirmDelete"
-]New value: +[
+  "watchIds",
+  "confirmed"
+]
  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 declare destructiveHint=true, and the description adds real value beyond that: the archiving mechanism, the permanence of the operation, the required explicit user confirmation, bounded batching, and partial-failure reporting. The only wobble is mild tension between 'archiving' and 'permanently deletes a root record'.

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 action and mechanism, and sized reasonably for a destructive tool. There is some duplication: the deletion/confirmation instructions are repeated almost verbatim in the confirmed parameter description, costing a little density.

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?

Covers the safety workflow, batch bounds, and even touches on return semantics ('one result per requested item', partial failures) despite an output schema existing. For a destructive batch tool this is close to complete; missing only return-shape detail that the output schema carries.

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 67%; workspaceId and confirmed are well documented in the schema itself, but watchIds has no description in either place. 'Batch edits are bounded' restates the maxItems:25 constraint without adding meaning, so the description adds little beyond the schema.

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?

States a specific verb and resource ('Delete person signal watches') and explains the mechanism ('by archiving them so they no longer refresh'), which separates it from edit_signal_watch. It does not explicitly route against sibling delete tools (delete_signal_agent, delete_company_employee_watch), so it stops short of a 5.

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 an explicit precondition ('Call this only after the user confirms the exact watches to remove'), which is clear usage context. It does not name an alternative tool for modifying rather than removing watches, so no exclusion/alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All campaignstack toolsInspect
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