Skip to main content
Glama

Unpublish Physical Product

unpublish_physical_product
Destructive

Unpublish a physical product. Requires confirm set to UNPUBLISH. 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>",
      "productId": "<productId>"
    },
    "name": "unpublish_physical_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.
productIdYesProduct ID, from a Nas.com product listing for this business.
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 / productId / description
      Added value: +"Product ID, from a Nas.com product listing for this business."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real value by layering entitlement gating, a mandatory confirmation literal, and a hard stop on blocked access. It stops short of describing the resulting state change (e.g. whether the product reverts to draft, what happens to existing orders or live listings), which matters for a destructive action.

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 purpose is front-loaded in the first sentence and the remaining sentences are sequential preconditions, each carrying a distinct instruction. It is slightly dense with imperative clauses but no sentence is pure filler.

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, entitlement-gated mutation with no output schema, the description covers the prerequisites an agent needs before calling it. The main gap is the absence of post-condition information about what unpublishing does to the product and its dependent resources.

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 coverage is 100%, so the baseline is 3, and the description does try to add meaning by specifying that confirm must be set to 'UNPUBLISH'. However, the schema's own confirm description says 'for example DELETE', which conflicts with the stated literal and leaves the agent unsure which value is correct; that ambiguity cancels much of the added value.

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?

States a specific verb and resource ('Unpublish a physical product') plus the required confirmation literal, so an agent knows exactly what operation this is. It does not explicitly distinguish itself from publish_physical_product or delete_physical_product, so the agent must infer the boundary from the names alone.

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 and exclusions: check business permissions first, call check_business_tool_access before collecting inputs, FREE businesses are blocked regardless of feature rows, show grace-period warnings and the resubscribe link, and never proceed when access is blocked. It names both the required prerequisite tool and the condition under which the tool must not be used.

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