Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_campaigns_delete_campaign

DestructiveIdempotent

Deletes a campaign by ID and detaches its placements, leaving them active and working independently.

Instructions

[Merchant] Delete a campaign. Its placements stay, detached from it, and keep working.

Endpoint: DELETE /campaigns/{campaignId} (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": {
      "campaignId": "<campaignId>"
    },
    "name": "payware_campaigns_delete_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's ID: cp + 8 letters or digits, e.g. cp7e4rCToG
useSandboxNoUse the sandbox (the default) rather than production

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds the one thing they cannot: the cascade consequence that placements remain and keep serving after detach. The plan requirement ('PRM plan') and the endpoint path further ground the behavior. It does not state whether deletion is reversible or what a re-delete returns, keeping it below a 5.

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 plus a compact endpoint line, with the consequential fact (placements survive) front-loaded right after the action. Nothing is redundant with the schema or annotations.

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 tool with no output schema, the definition covers the action, the side effect on related entities, and the plan prerequisite. The remaining gap is recovery semantics — whether the campaign can be restored — which matters for a deletion call.

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 campaignId's pattern and example and the useSandbox default are fully documented in the schema. The description only echoes the path parameter and adds no format or behavioral nuance beyond that, which is the expected baseline when the schema does the work.

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?

Opens with a specific verb+resource ('Delete a campaign') and immediately qualifies scope by stating that placements are not deleted, which separates it from the sibling placement-deletion tools. It stops short of naming any sibling directly, so the differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

Usage context is only implied: the destructive nature and the '(PRM plan)' note suggest when it applies, but there is no explicit when-to-use guidance, no when-not-to-use, and no pointer to alternatives like update_campaign for softer changes. An agent must infer that this is for permanent removal.

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