Skip to main content
Glama

Mute Listing

mute_listing

Mutes or unmutes one listing for the caller on XP -- 'hide this one', 'stop showing me that', 'unmute that listing'. Muting changes only the caller's view: the listing stays open, offers on it stand, and the seller and other buyers see no change. Muted listings are left out of list_open_listings. Sets the state passed rather than toggling, so repeating a call is safe. Requires sign-in.

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_identifier": "<listing_identifier>"
    },
    "name": "mute_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
mutedNoTrue to mute (hide it from the user's marketplace feed), False to unmute.
listing_identifierYesListing identifier from list_open_listings or get_open_listing.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by describing the exact blast radius: only the caller's view changes, the listing stays open, offers stand, and seller/other buyers are unaffected. It also discloses idempotency ('sets the state passed rather than toggling') and the sign-in prerequisite, none of which the annotations convey.

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 tight sentences: identity, user-intent examples, effect scope, then idempotency and auth. The most decision-relevant fact (the narrow, caller-only effect) is front-loaded with zero filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, non-destructive mutation with annotations and an output schema, the description covers purpose, scope of effect, idempotency, and auth. Nothing an agent needs to invoke it correctly is missing.

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 documents the muted boolean and listing_identifier source, so the schema carries most of the load. The description nonetheless adds useful semantics by framing the call as declarative state-setting rather than a toggle, which clarifies how the muted parameter should be reasoned about across repeat calls.

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 pair (mutes/unmutes) and resource (one listing) scoped to the caller, and reinforces it with concrete trigger utterances like 'hide this one'. An agent can immediately distinguish this from list_open_listings or cancel_my_listing.

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 when-to-use context through user-intent phrasings and explains the downstream effect (muted listings drop out of list_open_listings). It stops short of naming an explicit alternative or exclusion — for example, list_muted_listings for reviewing mutes or any bulk variant — so the routing guidance is strong but not complete.

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