SuperCatch

Prepare exact card price changes

supercatch_prepare_price_changes

Freeze up to 125 exact listing IDs, their expected versions and chosen USD decimal amounts. Creates a persisted plan; open its approval URL for trusted web review before execution. Use for an exact, frozen seller price workflow under this connection's separate price-write consent. No inventory, order, automation settings or listing publication changes. Local completion does not establish marketplace prices. Returns a strict baseline plan, durable operation or history envelope with explicit local outcomes. Stored approval tokens and worker lease IDs are never returned. Requires OAuth store:prices:write consent. Requires store:prices:write and current EDIT_LISTINGS permission on an approved owned store. Plans expire in nine minutes and contain up to 125 exact listing IDs. Each execution call processes at most five remaining targets. Reuse the original plan/key until terminal; released leases can continue immediately and abandoned leases wait two minutes. Status reads do not resume work. Plan and item reads are paginated. Persists an exact price plan for review in SuperCatch. It does not change listing prices. Foreign, revoked or expired grants and stale versions fail. Unapproved plans require web review. Idempotency-key reuse for another plan conflicts; a lost response is recovered through supercatch_list_operations or supercatch_get_operation before any new action.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "updates": [
        {
          "amount": "125.50",
          "listing_id": "owned-listing-id",
          "expected_version": "2026-11-03T16:00:00Z"
        }
      ]
    },
    "name": "supercatch_prepare_price_changes"
  }
}

Input Schema

Name	Required	Description	Default
`updates`	Yes	Frozen set of up to 125 distinct listing copies and exact prices to review in SuperCatch; execution continues in bounded batches without rerunning filters.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Adds substantial behavior beyond annotations: nine-minute plan expiry, 125-target cap, five targets per execution call, lease release/abandon timing, stale-version and foreign-grant failures, and the note that status reads do not resume work. However, its idempotency discussion sits awkwardly against idempotentHint=false without reconciling them, and the approval-URL handoff is described without saying how the URL is obtained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, but the body is a run-on sequence of short clauses with repetition (the 125 cap and the ‘no marketplace price change' point each appear twice). Facts are useful but would read better grouped into consent, lifecycle, and recovery blocks.

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?

Covers consent prerequisites, permissions, expiry, batch limits, failure modes and recovery paths, which is thorough for a mutating preparation tool with an output schema. Missing is explicit guidance on where the approval URL and plan/key come from in the response envelope, and any direct contrast with the sibling prepare tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by capping targets at 125 distinct entries, noting versions come from supercatch_get_listing, and explaining that execution consumes the frozen set in batches rather than re-filtering. The single-array shape and per-item fields are left to the schema.

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 concrete verb and resource: freeze up to 125 exact listing IDs with expected versions and USD amounts, producing a persisted plan. It also contrasts with sibling capabilities by explicitly excluding inventory, order, automation settings and publication changes, and clarifies that marketplace prices are not set locally.

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 clear context (exact frozen seller price workflow, separate price-write consent, web review before execution) and recovery routing to supercatch_list_operations / supercatch_get_operation. It never names the closest sibling, supercatch_prepare_card_price_updates, so the agent must infer which preparation tool applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SuperCatch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?