Skip to main content
Glama

List a site in the public app directory

set_app_listing

Submit, update, or withdraw a domain's listing in the qu4zr app directory, which starts pending operator approval. Send only the domain ID to read the current listing.

Instructions

Asks for a domain's site to appear at qu4zr.com/apps (with its own page at qu4zr.com/apps/{slug}). The listing starts PENDING: an operator approves it, and any later edit sends it back for review. Only for a real, working site the user wants strangers to find — confirm with them first, and write the title/tagline as a user would search for it. Categories: developer-tools, productivity, business, education, health-fitness, lifestyle, entertainment, utilities. Pass withdraw:true to take it out. Omit everything but domainId to read the current listing.

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": {
      "domainId": "<domainId>"
    },
    "name": "set_app_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
taglineNo
categoryNo
domainIdYes
withdrawNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the PENDING approval state, that an operator must approve, that any later edit re-triggers review, and that withdraw:true removes the listing. Gaps remain on permission/auth requirements and on whether unspecified fields are cleared or preserved on a partial edit.

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?

Front-loaded with the outcome (where the site appears) before the operational rules, and nearly every sentence carries distinct information. The category enumeration is long but necessary given the schema lacks an enum; the sentence about title/tagline style and the user-confirmation rule are slightly compressed together.

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 six-parameter, unannotated mutation tool with no output schema, the description covers the lifecycle (pending, approval, re-review), the destructive path (withdraw), and the read path. What is missing is what the read mode actually returns and what authorization the caller needs to list a domain.

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 0%, so the description must compensate, and it largely does: it explains domainId as the target domain, prescribes the intent for title/tagline ('write as a user would search for it'), enumerates the valid category values even though the schema declares no enum, and explains withdraw:true. The 'description' string parameter is never mentioned, leaving one of six undocumented.

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: asking for a domain's site to appear in the public app directory at qu4zr.com/apps with its own /apps/{slug} page. It also disambiguates the tool's dual mode by stating that omitting everything but domainId reads the current listing, so an agent knows this is both a write and a read surface.

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 an explicit when-to-use gate ('Only for a real, working site the user wants strangers to find') plus a required confirmation step with the user before calling. It also routes the withdrawal and read cases within the same tool. It does not name any sibling tool as an alternative, so it falls short of the explicit-alternatives bar.

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