Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

projects_delete

Permanently delete a project and tear down its backend, database, and stored data. Confirm before use because removal is irreversible.

Instructions

Permanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject to delete — its UUID, name, or a unique prefix. Use a specific id to avoid accidental matches. Find ids via 'projects_list'.
accountIdNoBilling account id the project belongs to. Defaults to the active account set via 'accounts_use'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Permanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success."
    • changedInput schema / properties / accountId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"projects_delete"
  2. Changed3 schema fields changedv0.2.21
    • changedInput schema / description
      Previous value: -"Delete a project from the billing account"New value: +"Permanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success."
    • changedInput schema / properties / accountId / description
      Previous value: -"Billing account ID (uses active account if omitted)"New value: +"Billing account id the project belongs to. Defaults to the active account set via 'accounts_use'."
    • changedInput schema / properties / id / description
      Previous value: -"Project ID (UUID or prefix)"New value: +"Project to delete — its UUID, name, or a unique prefix. Use a specific id to avoid accidental matches. Find ids via 'projects_list'."
  3. First observedv0.2.6

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full load and does so well: it declares irreversibility, enumerates what is destroyed, notes the billing-account dependency, and even describes the success return shape. Nothing important about the operation's behavior is left implicit.

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?

Three sentences, front-loaded with the destructive nature, then preconditions, then return value. Every clause adds actionable information with no filler.

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?

Despite having no output schema and no annotations, the description covers destructiveness, prerequisites, safer-invocation advice, and even the return payload for a two-parameter tool. An agent has everything needed to call it correctly and safely.

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 already 100%, so baseline is 3. The description adds marginal value by restating the prefix-matching hazard and framing the id as the safer selector, but the per-parameter meaning (UUID vs name vs prefix, accountId default) largely duplicates the schema descriptions.

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?

Opens with a specific verb and resource ('Permanently delete a project') and immediately scopes it by naming the collateral resources torn down (backend instance, database, stored data). Easily distinguished from siblings projects_list, projects_create, and projects_use.

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?

States the precondition (requires an active billing account, set via 'accounts_use'), the confirmation requirement ('always confirm with the user first'), and the alternative matching strategy (specific id over short prefix). This is explicit when/when-not guidance an agent can act on without inference.

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