Skip to main content
Glama

Pause a listing

pause_listing
Destructive

Hide a seller product from your Printlooper storefront. Nothing is deleted; resume_listing shows it again. Shopify listings are not changed. 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": "pause_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds genuinely useful context (state is preserved, reversible via resume_listing, account required, Shopify unaffected). However, it does not reconcile its 'nothing is deleted' framing with the destructive annotation, nor state any permission or rate-limit details beyond 'needs a connected account'.

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?

Four short sentences, front-loaded with the effect, then reversibility, scope, and precondition. Every sentence carries distinct information with no repetition of the title.

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 single-parameter state toggle with annotations covering the safety profile and no output schema, the description covers effect, reversibility, and preconditions. The only meaningful omission is disambiguating the listing_id parameter.

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?

Schema description coverage is 0% and the single parameter listing_id is never explained in the description — it is not stated whether this is the Printlooper listing id or a Shopify product id, or what format it takes. With only one parameter the burden is small, but the description adds nothing here.

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 specific verb and resource ('Hide a seller product from your Printlooper storefront') and implicitly scopes it away from Shopify listings and from the sibling resume_listing. An agent can tell what this does and what it does not touch without opening the schema.

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?

Names resume_listing as the reversal path and explicitly excludes Shopify listings from the effect, which is real when-to-use context. It does not compare against update_listing or other mutating siblings, so the alternative-selection guidance is clear but not exhaustive.

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