Skip to main content
Glama

Delete product

well_delete_product
Destructive

Delete a product from the current workspace (soft delete).

Use this tool when the user asks to delete or remove a product, a service, a plan, a variant or a price. Find the product_id first with well_list_products. To stop selling a product but keep it, change its status to archived with well_update_product instead.

REQUIRED: product_id.

A product a connected tool synced in (synced: true) is not deleted: the next sync would bring it back. A product that variants, collection members or dated prices nest under is not deleted either: move or delete those first. In both cases the call fails and nothing is deleted.

When the delete of a row a connected tool synced in is refused, the failure carries next_step: a hide that takes the row out of Well's lists and figures and keeps it in the connected tool. Offer that hide to the person; once they say yes, call next_step.tool with next_step.input. Never hide without that yes.

Returns { success: true, product_id } on success, or { success: false, error } on failure.

Input Schema

NameRequiredDescriptionDefault
product_idYesThe product to delete, from well_list_products.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
codeNo
errorNo
successYes
product_idNo
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / near_candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "company_id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "company_id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / near_candidates_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds the context annotations cannot: it is a soft delete, synced rows and rows with variants/collection members/dated prices are refused, and in both refusal cases nothing is deleted. It further describes the next_step hide payload and the hard rule never to hide without an explicit yes.

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 action, then the when-to-use, then the constraints, then the refusal flow — a sensible ordering with no filler sentences. It is on the long side, and the trailing 'Returns { success: true, product_id }' sentence duplicates the output schema, which is a minor redundancy.

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 single-entity mutation with 5 parameters, the description covers the safety profile, preconditions, failure behavior, and the follow-up negotiation loop. Nothing an agent needs in order to call this correctly and safely is missing.

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 description coverage is 100%, so product_id, workspace_id, conversation_id, idempotency_key and workspace_scope are all documented in the schema itself. The description only restates that product_id is required and where to source it, adding nothing new about the other four parameters; baseline 3 applies.

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+resource (delete a product) with the exact scope (current workspace) and the mutation semantics (soft delete). It also explicitly distinguishes itself from well_update_product's archive path and from well_list_products, so an agent can route without opening a 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 the triggering user intents (delete or remove a product, service, plan, variant or price), a prerequisite (find the product_id with well_list_products first), and an explicit alternative for the adjacent need (archive via well_update_product to stop selling but keep). The refusal path and the consent gate for the offered hide are also spelled out.

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