Skip to main content
Glama
Sign In
bearded-giant

spaceship-mcp

by bearded-giant
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create SellerHub Listing

create_sellerhub_domain

Lists a domain for sale on the SellerHub marketplace, making it publicly available for purchase and optionally setting buy-it-now or minimum offer pricing at creation.

Instructions

List a domain for sale on the SellerHub marketplace. This makes the domain publicly visible as available for purchase. The domain starts in 'verifying' status. You can optionally set pricing at creation time, or use update_sellerhub_domain later. Always confirm with the user before listing — verify the domain name.

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain name to list for sale.
binPriceNoBuy-it-now price (e.g. { amount: "9999", currency: "USD" }).
minPriceNoMinimum offer price (e.g. { amount: "100", currency: "USD" }).
descriptionNoDescription for the listing.
displayNameNoDisplay name for the listing.
binPriceEnabledNoEnable the buy-it-now price.
minPriceEnabledNoEnable the minimum offer price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses that the domain becomes publicly visible and starts in 'verifying' status, adding behavioral detail beyond annotations (destructiveHint=false, readOnlyHint=false). No contradictions with annotations.

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?

The description is three sentences, each earning its place: first states purpose, second adds behavioral context, third provides usage guidance. No wasted words, front-loaded.

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?

Given no output schema, the description adequately covers the tool's effect, status, and usage. It could mention return behavior or error handling, but it's sufficient for a creation tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for all parameters, including nested objects. The description adds no extra parameter details beyond mentioning optional pricing at creation; baseline 3 is appropriate.

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 explicitly states the verb 'List' and the resource 'domain for sale on the SellerHub marketplace', clearly distinguishing it from sibling tools like update_sellerhub_domain and delete_sellerhub_domain.

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?

The description provides clear context: it advises confirming with the user before listing, and mentions an alternative (update_sellerhub_domain) for setting pricing later. It does not explicitly state when not to use, but the guidance is strong.

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

Deploy Server

Other Tools