audit.domains - Domain Valuation

Set listing terms

set_listing_terms

DestructiveIdempotent

Set a listing's asking price, private floor and auto-accept rule, replacing the previous terms in full, so send every field you want to keep. Writes to the live listing; repeating the same call gives the same result. Needs the manage token. The floor is never shown to buyers. Use get_seller_listing instead to read the current terms first.

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": {
      "domain": "<domain>",
      "manageToken": "<manageToken>",
      "priceCents": "<priceCents>"
    },
    "name": "set_listing_terms"
  }
}

Input Schema

Name	Required	Description
`domain`	Yes	The seller's listed domain name, such as example.com.
`autoAccept`	No	true accepts offers at or above the floor automatically.
`floorCents`	No	Private minimum acceptable offer in US cents, at least 1000. Null sets no floor.
`priceCents`	Yes	Asking price in US cents, at least 1000 ($10).
`manageToken`	Yes	The listing's manage token. Sent as a bearer token; never repeat it in a message to anyone.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`buyUrl`	Yes
`status`	Yes
`proceeds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026
RemovedOct 6, 2026
First observedSep 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations it discloses what actually gets destroyed (all prior terms not resent), that the write hits the live listing, that a manage token is required for auth, and that the floor is private to buyers. The idempotency statement echoes the idempotentHint but frames it in observable terms.

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, each carrying a distinct operational fact: replacement semantics first, then write target, auth, privacy, and the read-first alternative. No filler or repetition.

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 and rich annotations, the description covers the remaining burden: destructive replace-all behavior, auth requirement, and the recommended read-before-write path. Nothing an agent needs to call this safely 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%, so the baseline is 3, but the description adds real meaning: omitted fields are wiped (so optional params must be resent deliberately) and the floor value is never exposed to buyers. It does not restate units or minimums, which the schema already covers.

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?

Names a specific verb (set) and resource (listing terms) and enumerates exactly which terms: asking price, private floor, auto-accept rule. It also contrasts with the sibling get_seller_listing, so an agent can route without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to call get_seller_listing first to read current terms, and warns that the call replaces terms in full so every field to keep must be sent. That is a clear when-to-use and how-to-use rule with a named alternative.

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

All audit.domains - Domain Valuation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?