Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_products_get_airing

Read-onlyIdempotent

Retrieve a single airing rule for a product placement by rule ID, with IDs and sandbox/production options, to inspect or verify placement settings.

Instructions

[Merchant] Get one airing rule.

Endpoint: GET /products/{productId}/placements/{placementId}/airings/{ruleId}

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>",
      "ruleId": "<ruleId>"
    },
    "name": "payware_products_get_airing"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesThe airing rule's ID, from payware_products_list_airings
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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing beyond restating the HTTP verb and path — no note on error behavior for unknown IDs, permissions, or whether a missing rule 404s versus returns empty.

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?

Two short lines, front-loaded with the purpose and then the endpoint. Nothing is padded, though the '[Merchant]' tag and raw endpoint line carry little decision value for an agent that already has the schema.

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?

For a simple single-resource read with full schema coverage and complete annotations, the definition is adequate. However, with no output schema, the description could have sketched what an airing rule contains, leaving the agent to guess at the return shape.

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%, with each of the four parameters documented including ID formats and the useSandbox default. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

States a concrete verb and resource ('Get one airing rule') and the endpoint path makes the resource hierarchy explicit. The singular 'one' distinguishes it from a list operation, though no sibling such as payware_products_list_airings is named.

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 only implied: an agent can infer this is for fetching a single known rule by ID rather than enumerating rules. There is no explicit when-to-use guidance, no mention of the list tool as the alternative for discovery, and no note about when sandbox vs production applies.

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