Skip to main content
Glama

campaignstack_delete_workspace

DestructiveIdempotent

Delete a workspace you own and cancel its subscription. Stops its workflows and scheduled work. Requires a user key or signed-in connection and confirmed:true. Confirm the exact workspace with the user before calling.

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": {
      "workspaceId": "<workspaceId>",
      "confirmed": "<confirmed>"
    },
    "name": "campaignstack_delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedYes
workspaceIdYes

Output Schema

NameRequiredDescriptionDefault
deletedNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the cascading effects (subscription cancelled, workflows and scheduled work stopped) and the auth/confirmation requirements — info the destructiveHint/openWorldHint flags alone do not convey. It still does not say whether the deletion or its data can be recovered, which matters for a destructive tool.

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?

Four short sentences with zero filler; the destructive consequence is front-loaded and the safety preconditions follow. Everything said is actionable.

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?

An output schema exists so return values need no explanation, and the description covers consequences, auth, and human confirmation for a destructive openWorld operation. The only meaningful gap is irreversibility and any effect on workspace members, which an agent would want before committing.

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 description coverage is 0%, so the description must carry both parameters, and it does: confirmed:true is tied to a mandatory user confirmation step, and workspaceId is framed as "the exact workspace" the user has verified, adding intent beyond the bare string type. The workspaceId requirement that it be an owned workspace is also conveyed.

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 a workspace") plus a notable side effect (cancels its subscription) and an ownership constraint. An agent can immediately separate this from the sibling edit_workspace / create_workspace / delete_workflow tools 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 clear preconditions for calling: the caller must own the workspace, must authenticate with a user key or signed-in connection, must pass confirmed:true, and must confirm the exact workspace with the user first. It stops short of naming an alternative action (e.g. archiving or editing via edit_workspace) for callers who do not want an irreversible delete.

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