SPACEXPLORATION

Create listing

create_listing

Create a new draft listing. Returns the full created listing exactly as stored, including its hashid and status. Pass an idempotency_key (any client-generated string, e.g. a UUID) to make the call safe to retry — re-sending the same key returns the original listing instead of creating a duplicate.

Input Schema

TableJSON Schema

Name	Required	Description
`apn`	No	The county assessor parcel number (APN / parcel ID), if known. Used with the county to find the building if another listing already has it.
`city`	Yes	City.
`unit`	No	Unit or suite number, if applicable.
`state`	Yes	State (2-letter abbreviation).
`county`	Yes	County.
`latitude`	Yes	Latitude coordinate.
`place_id`	No	Place ID from geocoder.
`longitude`	Yes	Longitude coordinate.
`postal_code`	Yes	ZIP/postal code.
`listing_type`	Yes	Listing type: sale or lease.
`property_type`	Yes	Property type. Allowed values are listed under the property_type attribute returned by get_registry (e.g. industrial, office, retail, land).
`street_address`	Yes	Street address of the property.
`idempotency_key`	No	Optional client-generated key (e.g. a UUID) making this create safe to retry: re-sending the same key within 24 hours returns the originally created listing instead of a duplicate.
`formatted_address`	No	Full formatted address string from geocoder.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / apn

Added value: +{
+  "description": "The county assessor parcel number (APN / parcel ID), if known. Used with the county to find the building if another listing already has it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedJun 17, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional client-generated key (e.g. a UUID) making this create safe to retry: re-sending the same key within 24 hours returns the originally created listing instead of a duplicate.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedJun 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false), and the description adds genuinely useful behavior: the exact return shape (full listing with hashid and status) and retry semantics. It stops short of explaining permissions required or what the draft state implies next, so it is not fully exhaustive.

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?

Three front-loaded sentences with no filler: purpose, return shape, then retry safety. The idempotency explanation is somewhat duplicated by the schema, which keeps this from being a clean 5, but nothing is wasted.

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 14-parameter, 9-required creation tool with no output schema, the description usefully describes the return payload (hashid, status) and idempotency window. It does not address the required-vs-optional split or draft lifecycle, but the schema and annotations cover the rest adequately.

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 description coverage is 100%, with each of the 14 parameters documented inline, so the schema carries the load. The description restates the idempotency_key behavior rather than adding syntax or edge cases beyond it, giving baseline value only.

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 ('Create a new draft listing'), and the word 'draft' distinguishes it from publish_listing and update_listing. It also states what comes back, so the agent knows this is a creation entry point rather than a mutation of an existing listing.

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

Usage Guidelines3/5

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

Usage is implied by the name and by the idempotency_key guidance ('Pass an idempotency_key ... to make the call safe to retry'), but there is no explicit when-to-use/when-not guidance relative to siblings like update_listing or publish_listing. Draft-vs-publish sequencing is left for the agent to infer.

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

All SPACEXPLORATION 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?