Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Search US homes for rent or sale

search_us_property_listings
Read-onlyIdempotent

Find US property listings to rent or buy by city, ZIP code, or search link, with price and bedroom filters and results showing address, price, beds, baths, size, status, and photos.

Instructions

US property listings for a city, ZIP code or search link, to rent or buy: address, price, beds, baths, size, property type, listing status, days on market, agent or broker, photos and link. Filters for price and rooms; newest first if asked. Runs the Apify Actor tacps126/realtor-scraper on your Apify account (about $0.001 per listing; spend per call is capped at $0.5).

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_us_property_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoSearch result links copied from the site.
locationsNoCities or ZIP codes, e.g. ["Austin, TX"].
max_itemsNoMaximum results to return (default 100, max 2000). Cost scales with this.
max_priceNoHighest price.
min_priceNoLowest price (monthly rent or sale price, USD).
min_roomsNoFewest bedrooms.
offer_typeNoRent or buy.rent
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
newest_firstNoNewest listings first.
property_typeNoApartment or house.apartment

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), and the description goes further by naming the backing Actor, the per-listing cost (~$0.001), and a hard per-call spend cap of $0.5. That cost/cap disclosure is genuinely useful context an agent cannot get from annotations. It does not cover failure modes or account/auth requirements beyond 'your Apify account'.

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 tight sentences: what you get, what you can filter, then cost/execution details. The field enumeration is long but front-loaded and scannable, and no sentence is filler.

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?

With an output schema present, the description need not explain return values, and it still covers inputs, cost, and the Actor behind the call. Minor gaps remain around whether urls and locations can be combined and how pagination or incomplete results are handled for a 10-parameter tool.

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%, so the schema already documents every parameter fully, including the cost note on max_items and enum values for offer_type and property_type. The description's 'filters for price and rooms; newest first if asked' merely restates those parameters without adding syntax or constraints. 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?

Specific verb-plus-resource: US property listings for a city, ZIP code or search link, for rent or buy. It enumerates the returned fields and names the geography, which is what separates it from search_german_property_listings without needing to open either 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?

Usage is implied by the geographic scope ('US property listings') and by the statement of supported inputs (city, ZIP, search link), but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative. An agent must infer that non-US housing queries belong elsewhere.

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