realtystack-mcp

Search active (or inactive) sale listings

search_sale_listings

Read-onlyIdempotent

Return a page of for-sale listings (list price, status, days on market, MLS name/number, listing agent + office contact, and price/status history) for a location. Same location-pinning rules as search_properties (address, city+state(+zipCode), or latitude+longitude+radius). Each record is tagged listingKind:"sale". Listings move faster than records, so these are cached only 30 minutes upstream.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_sale_listings"
  }
}

Input Schema

Name	Required	Description
`city`	No	City name; combine with state for an area search.
`limit`	No	Max listings to return per page. Default 50.
`price`	No	Listed price; supports ranges and multiple values.
`state`	No	2-character state abbreviation.
`offset`	No	Number of listings to skip, for pagination. Default 0.
`radius`	No	Search radius in miles (max 100); used with latitude/longitude.
`status`	No	Listing status to return; defaults to Active.
`address`	No	Full address to match a specific listing.
`daysOld`	No	Max days since the listing was last seen (min 1).
`lotSize`	No	Lot size in square feet; supports ranges and multiple values.
`zipCode`	No	5-digit ZIP code.
`bedrooms`	No	Bedroom count; supports ranges and multiple values.
`latitude`	No	Latitude of the search center; requires longitude and radius.
`bathrooms`	No	Bathroom count; supports fractions, ranges, and multiple values.
`longitude`	No	Longitude of the search center; requires latitude and radius.
`yearBuilt`	No	Year built; supports ranges and multiple values.
`propertyType`	No	Filter by property type.
`squareFootage`	No	Living-area square footage; supports ranges and multiple values.
`includeTotalCount`	No	When true, RentCast also returns the total matching count. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/idempotent/non-destructive annotations, the description discloses that listings are cached only 30 minutes upstream due to faster movement than records, and that each record is tagged with listingKind:"sale". This adds meaningful behavioral context beyond 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?

Three sentences; front-loaded with the main purpose and return fields. The reference to search_properties avoids repeating location rules, and the cache note is one brief sentence. No wasted words.

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?

For a 19-parameter search tool with no output schema, the description covers the core return fields, location constraints, record tagging, and caching behavior. It is sufficiently complete for an agent to understand what the tool does and how to invoke it effectively.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds value by explaining the valid location-pinning combinations (address, city+state(+zipCode), or latitude+longitude+radius), which is not obvious from inspecting each parameter individually. It does not repeat per-parameter details.

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 clearly states the tool returns a page of for-sale listings with specific fields (list price, status, days on market, etc.). It explicitly tags records as listingKind:"sale" and references search_properties for location rules, distinguishing it from the rental listing sibling.

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 gives clear context: it is for for-sale listings and follows the same location-pinning rules as search_properties (address, city+state(+zipCode), or latitude/longitude/radius). It implies use for current sale listings versus rentals, but does not explicitly name alternatives or state when not to use it.

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

All realtystack-mcp 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.