Skip to main content
Glama

List Muted Listings

list_muted_listings
Read-only

The listing identifiers the caller has muted on XP -- 'what have I hidden?'. Muting is a per-user view setting and does not change the listing itself. Muted listings are left out of list_open_listings and hidden on xp.tickets; get_market_read counts every fan listing, muted or not. Requires sign-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_muted_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that: it explains muting is a per-user view setting that does not alter the listing itself, describes how muting affects other surfaces, and states the sign-in requirement. Those are exactly the non-obvious behaviors an agent needs.

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?

Roughly three tight sentences: purpose and paraphrase first, conceptual clarification second, cross-tool effects third, precondition last. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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?

With an output schema present, return values need not be described, and annotations already cover safety and world scope. The description fills the remaining gaps — per-user scope, non-destructiveness of muting, cross-tool visibility, and the sign-in requirement — so an agent has everything needed to call it correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. The description correctly adds no invented argument detail, and the empty schema is consistent with the account-scoped nature described in the text.

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 gives a specific verb and resource — the listing identifiers the caller has muted — and frames it as a question ('what have I hidden?'), which removes ambiguity about what is returned. It also distinguishes the concept from listing data itself, so an agent can separate it from list_open_listings, get_market_read, and get_ticket_listings without inspecting schemas.

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?

Usage context is explicit: use this to answer 'what have I hidden?', and the description states that muted items are excluded from list_open_listings and hidden on xp.tickets while get_market_read ignores muting. That gives clear when-to-use and when-not-to-rely-on-it guidance. It stops short of naming the complementary mute_listing action, a minor gap, but the surrounding alternatives are named and characterized well.

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