Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_delete_product

DestructiveIdempotent

Deletes a product from a merchant account using its product ID, permanently removing the product record. Use for irreversible product cleanup.

Instructions

[Merchant] Delete a product from the merchant account. This action cannot be undone.

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": {
      "productId": "<productId>"
    },
    "name": "payware_products_delete_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerIdNoMerchant partner ID (uses PAYWARE_PARTNER_ID env var as default)partner_12345
productIdYesProduct identifier to delete (starts with 'pr')
privateKeyNoRSA private key for authentication (uses environment-specific private key as default)
useSandboxNoUse sandbox environment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds the concrete consequence ("cannot be undone"), which makes the destruction tangible, but says nothing about authentication requirements, error behavior on an unknown/in-use productId, or whether dependent airings/placements are affected.

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?

Two tight sentences with the action and its irreversible consequence front-loaded and zero filler. Nothing can be trimmed without losing information.

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 single-object destructive delete with full schema documentation and explicit destructive/idempotent annotations, the description covers what is needed to call it correctly. The remaining gap is only secondary behavior such as failure modes and the fate of related airings, which the annotations and schema otherwise carry.

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% and the description adds no parameter meaning, so the baseline of 3 applies. Notably it does not explain that the required productId must match the 'pr' prefix pattern or what the partnerId/privateKey auth parameters imply.

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 product from the merchant account" gives a specific verb and resource, and the resource noun 'product' separates it from the many delete_airing/delete_audio/delete_placement siblings. It does not explicitly name a sibling or contrast scope, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as whether to deactivate/update a product instead of deleting it. The only operative line is a warning about irreversibility, which is consequence information rather than selection guidance.

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