Skip to main content
Glama

Resume a listing

resume_listing
Destructive

Show a seller product you hid with pause_listing on your Printlooper storefront again. It cannot put a listing on the storefront for the first time; that happens on Printlooper. Showing it again publishes it again, so it takes the designer royalty as it is now (returned as royalty_percent). Needs a connected Printlooper account.

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": {
      "listing_id": "<listing_id>"
    },
    "name": "resume_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the crucial consequence beyond them: resuming republishes the listing and re-applies the designer royalty at the current rate, returned as royalty_percent. It also discloses the auth prerequisite (connected Printlooper account), which is exactly the context annotations cannot convey.

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?

Three tight sentences, front-loaded with the action, and each sentence carries real information (scope, exclusion, cost side effect, auth). Minor redundancy in the clause about first-time publishing, which partly repeats the resume framing.

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 one-parameter mutation with no output schema, the definition covers the key risks: republishing, royalty at the current rate (with the returned field named), and account prerequisites. It omits edge behavior such as what happens if the listing is not currently paused, but nothing essential to calling it is missing.

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

Parameters2/5

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

The single parameter listing_id has 0% schema description coverage and the description never explains it — no format, no indication of where to obtain the ID (e.g., from list_my_listings), and no note on the 80-character limit. Only the indirect phrase 'a seller product you hid' hints at what the ID refers to, so the coverage gap is not compensated.

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?

The description names a specific action (show a hidden listing on the storefront again), the exact resource (a seller product previously hidden via pause_listing), and explicitly carves out what it is not: first-time publishing, which happens on Printlooper. An agent can distinguish it from pause_listing and create_listing_draft without consulting other schemas.

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

Usage Guidelines5/5

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

It states the trigger condition (the listing was hidden with pause_listing) and the exclusion (this cannot publish a listing for the first time; that happens on Printlooper), plus a prerequisite (a connected Printlooper account). The alternative path for new listings is named explicitly, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources