RBSHome

Filter RBSHome leads

filter_properties

Read-onlyIdempotent

Find tax-delinquent property leads in Dallas County or Collin County, Texas that match a buy box (score, tier, property use, lot size, appraised value, ZIP, owner location, years delinquent and more), using the same filter as the RBSHome map. Call with count_only=true first to size the list, then page through results (25 per page by default, up to 1,000 rows per filter). Each row has a lead_id for get_property and a url that opens it in RBSHome. Call list_filter_fields before using attrs. Returns no sale prices, valuations, phone numbers or emails. Rows count toward a daily row limit. Read-only.

Input Schema

Name	Required	Description
`near`	No	Only leads within radius_mi of this property's map pin
`page`	No	Page, 1 to 40
`sort`	No	score (default), levy (tax balance), years (years delinquent) or next_sale (next tax-sale date)
`attrs`	No	Attribute filters keyed by registry key, e.g. {"flood_pct":{"max":5}} or {"flood_zone":{"not_in":["AE"]}}. Call list_filter_fields for the keys; never guess one.
`kinds`	No	Property kinds from the tax roll
`tiers`	No	Lead tiers; A is the most distressed
`counties`	No	Dallas, Collin or both. Omit for both.
`sort_dir`	No	Default desc; asc for next_sale (soonest first)
`acres_max`	No	Largest lot, acres
`acres_min`	No	Smallest lot, acres
`homestead`	No	Property has a homestead exemption on the county tax roll: true = only these, false = leave these out, null = either
`min_score`	No	Lowest lead score, 0 to 100. Default 45. Ignored while tiers is set, as on the map.
`page_size`	No	Rows per page, 1 to 50. page x page_size may not pass 1,000.
`count_only`	No	true returns only the count. Call this first to size the list.
`property_use`	No	Property use from the appraisal district
`zips_exclude`	No	Leave out these 5-digit ZIP codes
`zips_include`	No	Only these 5-digit ZIP codes
`is_delinquent`	No	Tax-delinquent: true = only these, false = leave these out, null = either
`portfolio_min`	No	Owner holds at least this many Dallas and Collin properties
`multiple_owners`	No	More than one owner on title: true = only these, false = leave these out, null = either
`saved_filter_id`	No	Start from this saved filter (ids from list_saved_filters); other fields change it
`years_owned_max`	No	Most years the owner has held it
`years_owned_min`	No	Fewest years the owner has held it
`exclude_keywords`	No	Owner name contains none of these words
`include_keywords`	No	Owner name contains any of these words
`include_unmapped`	No	Include leads with no map pin. Default false.
`market_value_max`	No	Highest appraisal-district market value, USD (not a price)
`market_value_min`	No	Lowest appraisal-district market value, USD (not a price)
`est_annual_tax_max`	No	Highest yearly tax levy, USD
`est_annual_tax_min`	No	Lowest yearly tax levy, USD
`jurisdiction_codes`	No	Taxing jurisdiction codes
`out_of_state_owner`	No	Owner mailing address outside Texas: true = only these, false = leave these out, null = either
`years_delinquent_min`	No	Fewest delinquent tax years
`include_institutional`	No	Include school districts, banks and hospitals. Default false.

Output Schema

Name	Required	Description	Default
`page`	Yes
`sort`	Yes
`count`	Yes
`notes`	Yes
`map_url`	Yes
`results`	Yes
`sources`	Yes
`next_page`	Yes
`page_size`	Yes
`truncated`	Yes
`data_as_of`	Yes
`count_source`	Yes
`applied_filter`	Yes
`map_url_dropped`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful non-annotation context: rows count toward a daily row limit, results are capped at 1,000 rows per filter, default page size is 25, and the tool returns no sale prices, valuations, phone numbers, or emails.

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?

The description is front-loaded with the core purpose and workflow, and most sentences carry operational value, including pagination, row limits, and return omissions. It is dense but appropriately sized for a complex 34-parameter tool; the closing 'Read-only' is redundant with annotations but minor.

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?

Given the tool's complexity, 34 parameters, and available output schema, the description is complete enough to guide correct use. It covers purpose, workflow, pagination, row quotas, return omissions, related tools for attrs and saved filters, and the lead_id handoff to get_property.

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 input schema already documents all 34 parameters, including attrs, pagination, filters, and defaults. The description adds a high-level list of filter categories and repeats the attrs registry warning, but it does not add syntax or format meaning beyond what the schema provides. A baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: finding tax-delinquent property leads in Dallas and Collin County that match a buy box, using the RBSHome map filter. It also distinguishes the row lead_id as input to get_property. However, it does not explicitly differentiate this tool from the sibling search_properties or motivated_sellers_near tools.

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?

It gives clear operational guidance: call with count_only=true first to size the list, then page through results, and call list_filter_fields before using attrs. It also says saved_filter_id comes from list_saved_filters and lead_id feeds get_property. It stops short of stating when to use this tool instead of siblings such as search_properties.

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

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