Skip to main content
Glama
Sign In
reelsaw

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete project forever

purge_project
DestructiveIdempotent

Permanently remove a deleted project and its files to free storage; call delete_project first, and optionally forget learned decisions.

Instructions

Permanently remove a deleted project and its files so the storage is freed (find it with list_deleted or list_projects deleted: true). Minutes, hourly creates and first-video-free are not refunded. A project that is not deleted is refused: call delete_project first. What you decided about it (accepted and rejected fixes, clip edits) stays in your decision log so Reelsaw keeps learning from it, unless forgetDecisions is true. Returns { storedBytes, forgottenDecisions, message }.

Input Schema

NameRequiredDescriptionDefault
idYesProject id (from list_projects with deleted: true)
forgetDecisionsNoAlso forget what Reelsaw learned from this project (its entries in the decision log); default false keeps them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.28.1
    • addedInput schema / properties / forgetDecisions
      Added value: +{
+  "default": false,
+  "description": "Also forget what Reelsaw learned from this project (its entries in the decision log); default false keeps them",
+  "type": "boolean"
+}
  2. Addedv0.26.3

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint/idempotentHint annotations, it discloses what is irrecoverable, that billing artifacts (minutes, hourly creates, first-video-free) are not refunded, and that decision-log entries survive unless forgetDecisions is set. That is exactly the side-effect detail annotations cannot express.

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?

Front-loaded with the destructive action and its scope, then preconditions, then side effects, then return shape. Dense and mostly waste-free, though the parenthetical and the return-value sentence pack several ideas into one long line.

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 supplies the return shape ({ storedBytes, forgottenDecisions, message }), the refusal case, and the non-refund policy, which covers everything needed to invoke a destructive purge correctly. Nothing material is left undocumented for a 2-parameter tool.

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 coverage is 100%, so baseline is 3; the description adds real meaning by framing forgetDecisions as a learning-retention tradeoff ('Reelsaw keeps learning from it, unless forgetDecisions is true') rather than just a flag. The id parameter's provenance is reinforced from both the schema and the guidance in the usage sentence.

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 ('permanently remove a deleted project and its files') plus the purpose (freeing storage), which cleanly separates it from delete_project (soft delete) and from purge_clip/purge_asset siblings. An agent can tell what it destroys without opening the schema.

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?

Gives explicit preconditions ('A project that is not deleted is refused: call delete_project first') and names the discovery tools to obtain the id (list_deleted or list_projects with deleted: true). It also states the condition under which the optional forgetDecisions behavior applies, leaving no routing inference to the agent.

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

Deploy Server

Other Tools