Skip to main content
Glama

Take a listing down

hollow_unlist
DestructiveIdempotent

Removes a market listing by its ID, letting you withdraw an item from sale and keep your available listings up to date.

Instructions

Remove one of your listings from the market by its id (from hollow_listings).

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": {
      "id": "<id>"
    },
    "name": "hollow_unlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing id, e.g. "l3k9x2m8q1z"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is known. The description adds only that the listing leaves the market; it does not say whether the removal is reversible, whether the listing record is deleted or just deactivated, or how active orders/agreements tied to it are affected.

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?

A single sentence, front-loaded with the action, followed by the qualifier and the id source. No filler, no restatement 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 one-parameter, destructive, idempotent operation whose annotations already disclose safety behavior and with no output schema to explain, the definition covers what it does and where the id comes from. The remaining gap is the side effects on related marketplace records, which matters for a destructive call.

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% and already supplies the pattern and an example id, so the schema carries the syntax. The description contributes real added meaning by naming hollow_listings as the provenance of the id, telling the agent where to obtain a valid value.

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 specific verb and resource ("Remove one of your listings") plus the scope ("from the market"), which is clearly distinct from hollow_listings and hollow_list. It stops short of contrasting with the teardown-style siblings such as hollow_unbuild or hollow_unrent, so it is clear but not fully disambiguated.

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 phrase "from the market" and the pointer to hollow_listings imply the when-to-use case (deactivating a marketplace listing) and where the id comes from. There is no explicit when-not guidance, no mention of what happens if there are pending orders or agreements, and no named alternative for other removal operations.

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