Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_update_audio

DestructiveIdempotent

Updates an audio title or transfers audio to another product in the same shop; requires a Premium plan.

Instructions

[Merchant] Update audio information (title) or reassign audio to another product. Premium (PRM) plan only: the server answers 403 on any other plan (for an ISV, the merchant's 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>",
      "audioId": "<audioId>"
    },
    "name": "payware_products_update_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew audio title
audioIdYesAudio identifier
partnerIdNoMerchant partner ID (uses PAYWARE_PARTNER_ID env var as default)partner_12345
productIdYesCurrent product identifier (starts with 'pr')
privateKeyNoRSA private key for authentication (uses environment-specific private key as default)
useSandboxNoUse sandbox environment
newProductIdNoProduct to move the audio to (starts with 'pr'). Sent as a transfer, which keeps the fingerprint; the target must be in the same shop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructive, idempotent, and openWorld behavior. The description adds a valuable failure mode (403 on non-PRM plans) but does not explain what exactly is destructive about reassignment, how title update differs from reassignment, or authentication requirements covered only in the schema.

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 purpose and followed by the plan constraint. No redundant wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a focused update tool, but given destructiveHint=true and seven parameters, the description should clarify whether title update and reassignment can be combined and what happens to the audio on reassignment. The schema fills some gaps, but the destructive behavior remains underspecified.

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 the schema already documents all seven parameters. The description mentions title and reassignment mapping to newProductId but adds no semantics beyond what the schema provides.

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?

The description states a specific verb and resource: update audio title or reassign audio to another product. It is clear enough to distinguish from register_audio, get_audio, and delete_audio, though it does not explicitly name alternatives.

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 is implied by the purpose and the plan prerequisite (Premium/PRM only with 403 otherwise), but there is no explicit when-to-use versus siblings guidance or when-not-to-use condition beyond the plan restriction.

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