Skip to main content
Glama

Delete Workspace

delete_workspace
DestructiveIdempotent

Delete a workspace of the organization with everything it holds: posts, RSS feeds, inbox items, API keys and connect links. This cannot be undone. The default workspace, the organization's last workspace and a workspace that still has connected social accounts cannot be deleted (400); disconnect its accounts with remove_account first. Confirm with the user first, naming the workspace and saying what it holds. Needs the workspace.manage permission, which Admin holds. The member who created the key, or the signed-in member, must also be an organization owner or admin (org-owner or org-admin); otherwise it fails with 403 permission_denied. Fails with 404 when the workspace is not in this organization. Returns { success: true }.

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": {
      "id": "<id>"
    },
    "name": "delete_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the workspace to delete, from list_workspaces. This is the target; workspaceId only picks the workspace the call acts in
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with success: true once the workspace is deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true, yet the description adds substantial context: the exact scope of data destroyed, that the action is unrecoverable, the guarding preconditions, and the 400/403/404 failure semantics. It also documents the return shape, which goes beyond what the flags convey.

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?

The destructive scope is front-loaded and nearly every sentence carries a distinct fact (cascade, irreversibility, blocking rules, permission, error codes). It is dense and long-ish, with the confirmation instruction mid-paragraph reading slightly apart from the failure-mode narrative, but there is little filler to cut.

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?

For a destructive, permission-gated mutation, the description covers preconditions, alternatives, error codes, and return value; an output schema exists so it need not describe response structure further. An agent has everything needed to decide and to call correctly.

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 100% and the schema already distinguishes id (the delete target) from workspaceId (the acting context) in detail, so the description adds no parameter-specific meaning. Baseline 3 applies since the schema carries the full burden here.

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?

Names a specific verb and resource and immediately enumerates the cascade (posts, RSS feeds, inbox items, API keys, connect links), which separates it from the narrower delete_post/delete_rss_feed siblings. The irreversibility statement reinforces what the operation actually is.

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 states the cases where deletion is blocked (default workspace, last workspace, workspace with connected social accounts), routes the agent to remove_account as the remedy, and requires user confirmation naming the workspace. It also names the required permission and role, so the agent knows the preconditions before calling.

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