list_domainsRetrieve all domains in a Spaceship account with pagination, sorting, and optional full-fetch to inspect or manage your domain inventory.
List all domains in the Spaceship account.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | Offset when fetchAll=false. | |
| take | No | Items per page when fetchAll=false. | |
| orderBy | No | Sort order. Prefix with '-' for descending. | |
| fetchAll | No | Fetch all pages. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral information beyond what is already indicated by annotations (readOnlyHint, openWorldHint). It does not mention pagination behavior, default fetchAll=true, or potential rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence of 8 words, containing zero wasted text. It is optimally front-loaded and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While the description covers the basic purpose, it lacks details on the return format or pagination behavior. For a list tool with no output schema, more context would be beneficial, but it is minimally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides 100% coverage with descriptions for all four parameters. The tool description adds no additional meaning, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List'), resource ('domains'), and scope ('in the Spaceship account'), making it easy to distinguish from sibling tools like 'get_domain' or 'check_domain_availability'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'list_sellerhub_domains' or how to handle pagination. The description lacks explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.