Skip to main content
Glama

Delete Zero Link

delete_zero_link
Destructive

Delete a Zero Link 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>",
      "zeroLinkId": "<zeroLinkId>"
    },
    "name": "delete_zero_link"
  }
}

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.
zeroLinkIdYesZero Link (payment link) ID.
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 / zeroLinkId / description
      Added value: +"Zero Link (payment link) ID."
  2. First observed

TDQS

A4.4/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 genuinely new behavioral context: a mandatory confirm literal, business-tier entitlement gating, a required pre-check call, and a grace-period/resubscribe surfacing obligation. That is well beyond what the structured flags convey.

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 gating requirement is front-loaded and every sentence carries operational weight. There is mild redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs,' which repeat the same instruction twice in slightly different words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, annotation-covered tool with a fully described 3-parameter schema and no output schema, the definition covers prerequisites, entitlement gating, confirmation, and blocked-access handling. The remaining gap is outcome behavior — whether the deletion is reversible and what the caller should expect afterward — which matters for a destructive action but is a single omission rather than a systemic one.

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 schema already documents all three parameters and a baseline of 3 would be defensible. The description adds real value by pinning confirm to the exact literal 'DELETE' where the schema only says 'for example DELETE,' tightening a destructive write's guardrail. It adds nothing about zeroLinkId or communityId beyond the schema's own guidance.

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?

The description opens with a specific verb and resource, 'Delete a Zero Link product,' which is enough to separate it from siblings such as delete_plan, delete_physical_product, or unpublish_zero_link. It stops short of a 5 because it never characterizes the scope of the deletion (permanent vs. recoverable) or its effect on dependent objects.

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 preconditions and exclusions: call check_business_tool_access before collecting inputs, FREE businesses cannot use the tool regardless of feature rows, show any grace-period warning and verified resubscribe link, and never proceed when access is blocked. An agent has a concrete, ordered decision procedure rather than an 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