MappaIQ

Add listing

add_listing

Create one Listing in one call. The address is geocoded by the server; latitude/longitude are optional. It starts Active and confirmed today, with the caller as Listing broker. An incomplete listing still saves, and shows on the Marketplace if its map is public; the result lists the missing fields, so ask the Broker for them.

Input Schema

Name	Required	Description
`city`	No
`name`	No	Listing name. Default: the address.
`notes`	No
`price`	No	Asking price in dollars. null = Call for pricing.
`stage`	No	Listing stage. Closed is not a stage: use close_listing.
`acreage`	No	Land size in acres.
`address`	Yes	Street address or intersection, e.g. 'Stacy Rd & US-75'.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`layerId`	No	Layer to add it to. Default: the account's first layer.
`latitude`	No	Optional. Latitude when known; else the address is geocoded.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`longitude`	No	Optional. Longitude when known; else the address is geocoded.
`offerType`	No
`assetClass`	No
`buildingSF`	No	Building size in square feet.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only mark it as a non-read, non-destructive write, so the description carries the real burden and delivers: server-side geocoding, default stage Active, confirmed-today status, caller becomes Listing broker, and the notable fact that an incomplete listing still saves and can surface publicly. It stops short of stating permissions or whether creation is reversible.

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 compact sentences, all front-loaded with the creation action and its key side effects. No wasted clauses, though the final sentence packs several distinct behaviors (partial save, Marketplace visibility, missing-field reporting) into one line.

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 16-parameter non-destructive write with no output schema, the description covers the high-value unknowns: geocoding, defaults, confirmation state, broker assignment, and partial-save behavior. It omits permission requirements and doesn't need to explain return values given no output schema.

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 75%, so most parameters are self-documented and the baseline is 3. The description adds useful semantics for lat/long (falls back to geocoding) and stage default, but does not illuminate the many enum or numeric fields beyond what the schema already states.

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+resource ('Create one Listing in one call') and the phrase 'one Listing in one call' implicitly distinguishes it from bulk-style siblings in the comp family. An agent can identify this as the single-listing creation tool without opening the schema.

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?

Gives implied usage context (geocoding is server-side, lat/long optional, starts Active/confirmed) but never names when to use this versus update_listing or close_listing, nor states prerequisites explicitly. The 'ask the Broker for them' hint frames a recovery workflow but not tool selection.

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

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