Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_delete_placement

DestructiveIdempotent

Delete a product placement to permanently invalidate its printed codes and payware link; the placement ID cannot be reused. Use active false instead to stop airing while keeping codes working.

Instructions

[Merchant] Delete a placement. Its printed codes and its payware link stop resolving, and its ID is never reused. To stop airing and attribution but keep printed codes working, replace it with active false instead.

Endpoint: DELETE /products/{productId}/placements/{placementId} (PRM plan)

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>",
      "placementId": "<placementId>"
    },
    "name": "payware_products_delete_placement"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesThe product's ID: pr + 8 letters or digits, e.g. pr7e4rCToG
useSandboxNoUse the sandbox (the default) rather than production
placementIdYesThe placement's ID: pl + 8 letters or digits, e.g. pl7e4rCToG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description goes further by disclosing downstream effects annotations cannot express: printed codes and the payware link stop resolving, and the ID is never reused. It also notes the PRM plan requirement, though it says nothing about failure modes such as deleting an already-deleted or in-use placement.

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 sentences, front-loaded with the consequential behavior (codes and link stop resolving) before the safer alternative, followed by a compact endpoint/plan line. No filler or restated boilerplate.

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, 3-parameter delete with no output schema, the definition covers consequences, ID lifecycle, the safer alternative, and plan gating — everything needed to decide and safely invoke it. Any remaining gap (error cases) is minor.

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%, with both IDs, their regex patterns, and the sandbox default fully documented in the schema. The description only echoes the endpoint path placeholders ({productId}/{placementId}) and adds no format, constraint, or dependency meaning beyond what is already structured.

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 and resource ("Delete a placement") and immediately distinguishes this operation's effect from the non-destructive alternative of deactivating via active=false, so an agent can tell delete from update_placement without opening either 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 an explicit when-not condition and names the alternative course of action: "To stop airing and attribution but keep printed codes working, replace it with active false instead." This is exactly the routing guidance an agent needs before an irreversible call.

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