campaignstack

Delete lead list

campaignstack_delete_lead_list

Destructive

Delete up to 50 lead lists from the bound workspace. The list row is removed and entries drain asynchronously. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`confirmed`	Yes	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.
`leadListIds`	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`	No
`items`	No
`failed`	No
`results`	No
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

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: -[
-  "leadListIds",
-  "confirmDelete"
-]New value: +[
+  "leadListIds",
+  "confirmed"
+]

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

AddedSep 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely new traits: the list row is removed immediately while entries drain asynchronously, and it is a permanent root-record deletion. This goes beyond the boolean hints, though the confirmation protocol is duplicated verbatim in the schema.

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?

Three sentences, front-loaded with purpose, scope, and behavior in a logical order. Slightly undermined by the confirmation sentence being repeated word-for-word in the confirmed parameter description, but within the description itself nothing is wasted.

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 and annotations covering the safety profile, the description supplies everything an agent needs: purpose, scope, async behavior, permanence, and the confirmation gate. Nothing material is missing for correct invocation.

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 coverage is 67%, and workspaceId plus confirmed carry rich schema descriptions. The description only reinforces the 50-item cap on leadListIds and adds no syntax or format detail; leadListIds itself has no schema description, so the gap is only partly compensated. Baseline 3 for adequate but not value-adding param guidance.

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 ('Delete ... lead lists') with explicit scope ('up to 50', 'from the bound workspace'). This is clearly distinguishable from siblings like campaignstack_get_lead_lists and campaignstack_edit_lead_list without opening any 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?

Gives a strong precondition for invocation: name exactly what will be deleted, state it cannot be undone, and wait for an explicit yes. It does not name alternative tools or contrast with soft-delete paths, so it falls short of a full when/when-not/alternatives treatment.

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?