Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_replace_airings

DestructiveIdempotent

Replace all airing rules for a placement in one atomic call; if any rule is refused, nothing is saved. Submit an empty list to remove every rule.

Instructions

[Merchant] Replace all of a placement's airing rules with this list, all or nothing: when any rule is refused, nothing is saved and each refused rule is listed by its index. An empty list removes every rule. Suited to loading an agency's schedule in one call.

Endpoint: PUT /products/{productId}/placements/{placementId}/airings (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>",
      "rules": "<rules>"
    },
    "name": "payware_products_replace_airings"
  }
}

Input Schema

NameRequiredDescriptionDefault
rulesYesThe complete new set of airing rules, up to 100
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.3/5.0
Behavior5/5

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

Goes well beyond the destructive/idempotent annotations by disclosing transactionality ('when any rule is refused, nothing is saved and each refused rule is listed by its index') and the surprising empty-list semantics. That is exactly the context an agent needs before a destructive bulk write.

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 verb and the atomicity guarantee, and every sentence carries weight. The trailing endpoint/'(PRM plan)' line is mildly extraneous but not distracting.

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 bulk-mutation tool with no output schema, the description covers failure reporting and the empty-list case, which are the main unknowns. It says little about the success response or auth requirements, but nothing critical is missing for correct invocation.

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% and the field descriptions already cover dates, windows, recurrence and IDs in depth, so the description only restates that rules is 'the complete new set'. It adds no format or default detail beyond the schema, which is acceptable here.

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 ('Replace all of a placement's airing rules with this list') plus the exact endpoint, and the 'all' scoping tells an agent it differs from single-rule siblings like update_airing or create_airing.

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

Usage Guidelines4/5

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

Gives a concrete usage scenario ('loading an agency's schedule in one call') and implicitly steers bulk work here rather than to per-rule tools, but it never names an alternative or states when not to use it, e.g. for adding one rule.

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