SuperCatch

Inspect a frozen submission plan

supercatch_get_listing_submission_plan

Read-onlyIdempotent

Inspect a page of the exact frozen draft membership and versions. Keep the page size when following next_cursor; this never changes membership or submits drafts. Submit an explicit frozen set of existing owned DRAFT listings that already pass SuperCatch's native readiness checks to its internal moderation queue. Does not approve or activate listings, publish to marketplaces, bypass moderation, repair blockers, change prices or stock, or select by a live search filter. A strict listing.draft.submit plan or durable per-item operation receipt. Public pages contain at most five items with whole-selection totals and a bound continuation cursor; private policy fingerprints stay on the server. Requires OAuth store:listings:drafts:submit consent. Requires separate store:listings:drafts:submit consent, an approved owned store and current EDIT_LISTINGS permission. Draft-edit, price and inventory consent do not imply submission authority. Frozen membership is limited to 100 targets; plans expire after nine minutes. Native activity provides inspection and continuation without bypassing the original grant. Read-only inspection; does not continue submission. Missing drafts, stale versions or readiness changes fail without substituting other targets. After a lost response, recover the original key or operation. A repeated execution continues only queued items; completed items are never submitted again. Unknown outcomes require reconciliation before new intent.

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": {
      "limit": 5,
      "plan_id": "submission-plan-id"
    },
    "name": "supercatch_get_listing_submission_plan"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum frozen targets or receipts on this page; keep this value when continuing its cursor.
`cursor`	No	Opaque next_cursor from this exact plan or operation and the same page size. It cannot change the frozen selection.
`plan_id`	Yes	Exact connection-bound plan ID returned by supercatch_prepare_listing_submission.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses meaningful operational constraints: pages contain at most five items, plans expire after nine minutes, frozen membership is limited to 100 targets, missing drafts or stale versions fail without substitution, and specific OAuth consent plus EDIT_LISTINGS permission are required. Some of this context is muddled by submission-execution language, but the extra behavioral detail is substantial.

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

Conciseness2/5

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

The description is a long run-on block that mixes read-only inspection with submission execution details. It repeats consent requirements ('Requires OAuth store:listings:drafts:submit consent. Requires separate store:listings:drafts:submit consent...') and buries the core inspection purpose under unrelated submission semantics.

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?

Given the tool's complexity, the description covers the important operational facts: page size, cursor continuation, expiry, target limits, permission requirements, and failure behavior. An output schema exists, so return values need not be explained. The main gap is that the submission-oriented language creates ambiguity about what this specific read-only tool does.

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, but the description adds useful meaning: keep the page size when following next_cursor, the cursor is opaque and tied to the exact plan or operation, and plan_id is an exact connection-bound ID returned by supercatch_prepare_listing_submission. This goes beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource: 'Inspect a page of the exact frozen draft membership and versions.' However, the description immediately shifts into 'Submit an explicit frozen set of existing owned DRAFT listings...', which describes submission rather than inspection and blurs what this read-only tool actually does. It also does not explicitly distinguish itself from siblings like supercatch_get_listing_draft_plan or supercatch_execute_listing_submission.

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?

The description implies inspection and continuation usage with 'Read-only inspection; does not continue submission' and 'Native activity provides inspection and continuation without bypassing the original grant.' It does not explicitly state when to choose this over supercatch_get_operation, supercatch_get_listing_draft_plan, or supercatch_execute_listing_submission, so the guidance remains implied rather than explicit.

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?