Skip to main content
Glama

Delete Folder Product

delete_folder_product
Destructive

Delete a folder-backed product. Requires confirm set to DELETE. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "folderId": "<folderId>"
    },
    "name": "delete_folder_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
folderIdYesDigital product (folder) ID, from a Nas.com product listing.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / folderId / description
      Added value: +"Digital product (folder) ID, from a Nas.com product listing."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds behavior the annotations cannot express: a required confirmation literal, business-tier eligibility that overrides feature rows, an obligation to surface grace-period warnings and a verified resubscribe link, and an explicit prohibition on continuing when blocked. That is substantial operational context beyond the structured fields.

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 action is front-loaded in the first sentence and the remaining sentences each carry a distinct constraint, with no filler. There is mild redundancy between "check business permissions" and "Call check_business_tool_access," and the permission/grace-period material is packed densely enough that the ordering of steps takes a second read.

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, no-output-schema mutation with three fully described parameters, the description supplies the confirmation requirement, the access-gating sequence, the blocked-path behavior, and the user-facing warning obligations. An agent has everything needed to decide whether to call it and how to proceed 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 100%, so the baseline is 3; the description earns above that by pinning confirm to the exact literal DELETE, where the schema only says "for example DELETE". It adds no further semantics for communityId or folderId, which the schema already documents well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete a folder-backed product" gives a specific verb plus a specific resource, and the qualifier "folder-backed" separates it from a physical-product deletion. It stops short of naming the near neighbors (delete_folder_item, delete_physical_product), so an agent must still infer what a "folder product" is versus a "folder item".

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 states the precondition (confirm must be the literal DELETE), the gating step (call check_business_tool_access before collecting inputs), an explicit exclusion (FREE businesses cannot use this tool regardless of feature rows), and a hard stop (never proceed when access is blocked). Alternatives are named directly, so nothing about when-to-use is left to inference.

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