Skip to main content
Glama

delete_idea

Destructive

Delete one or more ideas from the Ideas tab of the active workspace, by the ids list_ideas and save_idea give. Use it to undo a wrong save_idea. All or none: if any id is not found on this workspace, or is someone else's idea and the user is not an account admin, nothing is deleted and the reply names which ids. There is no undo: each idea's sources, tags and images are deleted with it.

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": {
      "ids": "<ids>"
    },
    "name": "delete_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesIdea ids to delete, up to 100 per call.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing all-or-nothing atomicity, the permission gate for another user's idea, that a failed call names the offending ids, and that sources, tags and images are cascaded with no undo. These are precisely the failure modes an agent needs before invoking a destructive call.

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 sentences, front-loaded with the action and scope, then the intended use case, then the atomicity contract, then the irreversibility warning. No sentence is redundant and the most severe fact (no undo) lands last for emphasis.

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 two-parameter tool with no output schema, the description covers atomicity, partial-failure reporting, permission preconditions and cascade effects, so an agent knows both the outcome and the error shape. Nothing material is left to inference.

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%, so both parameters are already fully documented, including the 100-item cap and the workspace scoping rules. The description only adds provenance for the ids (they come from list_ideas/save_idea), which is useful but marginal, so the baseline of 3 applies.

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 one or more ideas'), narrows the location ('Ideas tab of the active workspace'), and anchors the input source to two named siblings ('ids `list_ideas` and `save_idea` give'). An agent can distinguish this from update_idea or delete_post 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 an explicit positive use case ('Use it to undo a wrong save_idea') and points to list_ideas as the id source. It does not say when not to use it (e.g., correcting a saved idea via update_idea instead of deleting), so it stops short of full routing guidance.

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