Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

campaignstack_delete_company_employee_watch

Destructive

Delete company employee 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

A4/5.0
Behavior4/5

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

Annotations already establish destructiveHint=true and non-idempotency, but the description adds value beyond them: the archive-based mechanism, bounded batch edits, one result per item, and the instruction to report partial failures rather than claiming whole-batch success. The mild internal tension between 'archiving' and 'permanently deletes a root record' is a wording wrinkle, not a contradiction of 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the confirmation requirement is stated twice in near-identical terms ('Call this only after the user confirms the exact watches to remove' vs 'name exactly what will be deleted ... wait for an explicit yes'), which is redundant bulk for a six-sentence description.

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 destructive batch delete gated by explicit confirmation, the description covers irreversibility, batch bounds, and partial-failure reporting, and an output schema exists to cover return shape. The only gap is the absence of any hint about the workspaceId parameter's multi-workspace requirement, which is 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 67%, so the schema already does most of the work, and the description never discusses watchIds or the workspaceId fallback logic. It only implies the batch nature ('Batch edits are bounded', 'one result per requested item'), and the confirmation text duplicates the 'confirmed' parameter's own schema description. Baseline 3 fits.

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?

Specific verb plus resource ('Delete company employee watches') with the mechanism disclosed ('by archiving them so they no longer refresh'). This cleanly separates it from siblings like campaignstack_edit_company_employee_watch and campaignstack_get_company_employee_watches, so an agent can route without opening a schema.

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?

'Call this only after the user confirms the exact watches to remove' gives a clear precondition for use. It does not, however, name the alternative to reach for when the user only wants to modify a watch rather than remove it (e.g. edit_company_employee_watch), so the when-not/alternative half of the guidance is missing.

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