Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

delete_cell

Destructive

Deletes a block and all its children, assignments and linked dependencies. The deletion is PERMANENT: no trash and no undo by the tool (only a version saved before the call, via restore_version — which replaces the WHOLE schema —, gets back what was deleted). It takes away what is listed here and what depends on the block (its content, its sharing grants, its block links); the attached comments, tasks and documents are not destroyed (they survive, detached). This is NOT an erasure of personal data: that goes through deleting the account or the project. Returns the complete list of what was deleted. dryRun:true PREVIEWS exactly what would be taken away (same report, nothing is deleted): a way to warn the user of a cascading deletion. If comment threads were anchored on the deleted blocks, they SURVIVE (they are not destroyed) but become invisible on the canvas: the response flags it via orphanedComments + note when that is the case. Same for the linked TASKS (create_tasks): they survive (they are not deleted), become "no subject" and re-attach automatically if a block with the same id is recreated — flagged via detachedTasks + note when that is the case.

Input Schema

NameRequiredDescriptionDefault
idYesID of the block to delete
dryRunNoIf true, computes and returns the EXACT cascade (blocks, assignments, dependencies) WITHOUT DELETING ANYTHING. Useful to warn a user of what a delete_cell would take away ahead of actually running it — omitted or false, the deletion is real (behavior unchanged).
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / dryRun / description
      Previous value: -"Si true, calcule et retourne la cascade EXACTE (cellules, assignments, dépendances) SANS RIEN SUPPRIMER. Utile pour prévenir un utilisateur de ce qu'un delete_cell emporterait AVANT de l'exécuter réellement — omis ou false, la suppression est réelle (comportement inchangé)."New value: +"If true, computes and returns the EXACT cascade (blocks, assignments, dependencies) WITHOUT DELETING ANYTHING. Useful to warn a user of what a delete_cell would take away ahead of actually running it — omitted or false, the deletion is real (behavior unchanged)."
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
    • changedInput schema / properties / id / description
      Previous value: -"ID de la cellule à supprimer"New value: +"ID of the block to delete"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true, but the description discloses far more: permanence with no trash/undo, the exact cascade (content, sharing grants, block links destroyed), what survives detached (comments, tasks, documents), and the orphanedComments/detachedTasks response flags. This is unusually rich behavioral context.

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?

It is front-loaded with the core action and most sentences carry real information. However, the dense parentheticals and repeated clauses ('they survive (they are not destroyed)' twice) add length without new meaning.

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 no output schema, the description covers the return value ('Returns the complete list of what was deleted') and the conditional response fields. Everything an agent needs to invoke a destructive cascade safely is present.

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 100%, so id, dryRun, and expectedProjectId are already fully documented in the schema itself. The description's dryRun explanation largely duplicates the schema text and it never mentions expectedProjectId's targeted-project override, so it adds little beyond the baseline.

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?

The first sentence states a specific verb, resource, and cascade scope: 'Deletes a block and all its children, assignments and linked dependencies.' This lets an agent distinguish delete_cell from siblings like delete_content_block or delete_dependency, which target different resources.

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?

It gives explicit when-not guidance ('This is NOT an erasure of personal data: that goes through deleting the account or the project') and an alternative recovery path (restore_version), and it prescribes dryRun:true as the way to preview a cascading deletion before committing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OrgGen AI 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