Skip to main content
Glama

Create search automation

spur_create_search_automation
Destructive

Schedule a recurring property search. Event automations default to the legacy engine to retain event tracking. Data-platform mode supports recipe_key/params/selections, credit budgets, unknown-result lists, automatic contacts with a credit cap and conditions, and channel outreach routes. Each enabled run spends credits/actions and can contact people; approve the settings before enabling. Use params={source:"data_search",location:{...},filters:{...}} for exact Data Search filters. Legacy listing/event filters remain supported.

Examples:

  • "every Monday 8am Central, Dallas rentals under $2k" -> frequency="weekly", day_of_week=1, run_time="08:00", timezone="America/Chicago", location="Dallas, TX", max_amount=2000

  • "last Friday of each month" -> frequency="monthly", day_of_week=5, week_of_month=-1

  • "every morning, new pre-foreclosures and price drops in Houston, save to my Distress list" -> frequency="daily", run_time="07:00", location="Houston, TX", events=["preforeclosure","price_drop"], list_id=…

Accepts the same advanced and event filters as spur_search_properties (min_amount / max_amount instead of min_price / max_price). Run the search once with spur_data_search first so the user can check the results before scheduling.

In automations each event fires once, on the run that first sees it, so the same property isn't saved twice; change events start reporting from the second run. "delisted" is only available here.

Events (pass in events; a listing matches when ANY selected event fired, and is tagged with each):

  • Listing lifecycle: new_listing, coming_soon, coming_soon_active, price_drop, price_increase, pending, sold, back_on_market, delisted (automations only), open_house, rental_listed, rent_change, move_in_moved_up

  • Distress & motivation: preforeclosure, foreclosure, auction, bank_owned, distress_escalated, fsbo, agent_to_fsbo, stale_listing, new_construction

  • Valuation & tax: tax_assessment_posted, assessed_value_jump, tax_paid_dropped (weak), sale_recorded, zestimate_moved, equity_gap, price_below_assessed Direct events (price_drop, pending, sold, preforeclosure, fsbo, new_listing, …) work on the first search. Change events (price_increase, back_on_market, distress_escalated, agent_to_fsbo, rent_change, zestimate_moved, …) compare against what Spur saw on an earlier search of the same area, so the first search only records a baseline. Motivated-seller research usually combines price_drop, back_on_market, stale_listing, agent_to_fsbo and the distress stages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "location": "<location>",
      "frequency": "<frequency>",
      "run_time": "<run_time>"
    },
    "name": "spur_create_search_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAutomation name shown in Spur
engineNo
eventsNoOnly listings where any of these events happened; see the tool description
paramsNoRecipe parameters including location, or {source:"data_search", location:{...}, filters:{...}} for exact Data Search filters
confirmNoRequired when enabled=true: approve the recurring search, budgets and automatic outreach first
enabledNofalse = save it paused
list_idNoSave new matches into this property list
max_ageNoAt most this many years since built
max_zipNoHighest ZIP code in a numeric ZIP range (with min_zip)
min_ageNoYears since built
min_zipNoLowest ZIP code in a numeric ZIP range (with max_zip); prefer zip_list for specific ZIPs
ai_queryNoQualitative intent; each run re-ranks listings by description against it
has_poolNotrue = only listings with a pool
has_viewNotrue = only listings with any view (use views on live search for a specific kind)
keywordsNoComma-separated listing keywords, e.g. "pool, granite"
locationYesCity/state or ZIP, e.g. "Dallas, TX"
max_bedsNoMaximum bedrooms
max_sqftNoMaximum living area in square feet
min_bedsNoMinimum bedrooms
min_sqftNoMinimum living area in square feet
run_timeYes24h local time "HH:MM"
timezoneNoIANA time zone, e.g. "America/Chicago"UTC
zip_listNoKeep only these ZIPs; set location to the city that contains them
auto_saveNoSave new matches to the user's properties
frequencyYesHow often the search runs
home_typeNoZillow home type code
max_bathsNoMaximum bathrooms
min_bathsNoMinimum bathrooms (half baths count as 0.5)
center_latNoRadius search centre (with center_lng and radius_miles)
center_lngNoRadius search centre longitude (with center_lat and radius_miles)
has_garageNotrue = only listings with a garage
max_amountNoMaximum price in USD (rent per month for forRent)
min_amountNoMinimum price in USD (rent per month for forRent)
min_equityNoEstimated equity in USD (Zestimate or price minus assessed value; rough)
recipe_keyNo
selectionsNo
auto_enrichNoSkip-trace new matches on every run (spends enrichment credits)
day_of_weekNo0=Sunday … 6=Saturday; for weekly, biweekly, monthly
days_postedNoOnly listings posted within this many days
only_vacantNoLikely vacant (heuristic: description keywords + long days on market)
listing_typeNoSeller / listing kind; for catching NEW entries into a distress stage prefer events
max_lot_sizeNoSquare feet
min_lot_sizeNoSquare feet (1 acre = 43,560)
radius_milesNoKeep only listings within this many miles of center_lat / center_lng
auto_contactsNo
is_waterfrontNotrue = only waterfront listings
neighborhoodsNoNeighborhood / area names matched against address and description
only_absenteeNoAbsentee-owned (owner mails elsewhere)
week_of_monthNoMonthly only; -1 = last
listing_statusNoWhich listings to search
max_year_builtNoBuilt in or before this year
min_year_builtNoBuilt in or after this year
ownership_typeNobusiness = LLC / corp / trust owners (heuristic)
unknown_policyNo
outreach_routesNo
unknown_list_idNo
event_stale_daysNoDays on market that counts as stale (default 90)
is_price_reducedNotrue = only listings whose asking price has been cut
event_within_daysNoLookback window for events, in days (default 7)
contacts_conditionNo
max_days_on_marketNoListed at most this many days
min_days_on_marketNoListed at least this many days (higher suggests a motivated seller)
max_ownership_yearsNoOwner has held the property at most this long
min_ownership_yearsNoOwner has held the property at least this long
budget_limit_creditsNo
event_min_change_pctNoMinimum % move for price / rent / Zestimate / assessment events
only_pre_foreclosureNoDistressed / pre-foreclosure (heuristic, includes description keywords)
contacts_budget_creditsNo
event_min_equity_gap_pctNoMinimum % Zestimate above last sale price for equity_gap (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / properties / auto_contacts
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / budget_limit_credits
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / confirm
      Added value: +{
      +  "const": true,
      +  "description": "Required when enabled=true: approve the recurring search, budgets and automatic outreach first",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / contacts_budget_credits
      Added value: +{
      +  "anyOf": [
      +    {
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / contacts_condition
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "key": {
      +            "maxLength": 100,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "label": {
      +            "maxLength": 80,
      +            "type": "string"
      +          },
      +          "op": {
      +            "maxLength": 30,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "path": {
      +            "maxLength": 100,
      +            "type": "string"
      +          },
      +          "value": {}
      +        },
      +        "required": [
      +          "key",
      +          "op"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 10,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / engine
      Added value: +{
      +  "enum": [
      +    "legacy",
      +    "data_platform"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / listing_status / default
      Removed value: -"forRent"
    • addedInput schema / properties / outreach_routes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "order": {
      +          "items": {
      +            "enum": [
      +              "sms",
      +              "email",
      +              "mail"
      +            ],
      +            "type": "string"
      +          },
      +          "maxItems": 3,
      +          "type": "array"
      +        },
      +        "routes": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "email": {
      +              "maxLength": 64,
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "mail": {
      +              "maxLength": 64,
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "sms": {
      +              "maxLength": 64,
      +              "minLength": 1,
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "routes"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / params
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Recipe parameters including location, or {source:\"data_search\", location:{...}, filters:{...}} for exact Data Search filters",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / recipe_key
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / selections
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "allowFallback": {
      +            "type": "boolean"
      +          },
      +          "fallbackPolicy": {
      +            "enum": [
      +              "stop",
      +              "listed",
      +              "any"
      +            ],
      +            "type": "string"
      +          },
      +          "mode": {
      +            "enum": [
      +              "automatic",
      +              "preferred",
      +              "locked"
      +            ],
      +            "type": "string"
      +          },
      +          "providers": {
      +            "default": [],
      +            "items": {
      +              "maxLength": 64,
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "maxItems": 10,
      +            "type": "array"
      +          }
      +        },
      +        "required": [
      +          "mode"
      +        ],
      +        "type": "object"
      +      },
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / unknown_list_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedInput schema / properties / unknown_policy
      Added value: +{
      +  "enum": [
      +    "save_separately",
      +    "drop"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=true, openWorld=true; the description adds the crucial economics and side effects — every enabled run spends credits/actions and may contact people, and auto_enrich/auto_contacts spend enrichment credits. It also explains event firing semantics (each event fires once on the first run that sees it, change events need a baseline run, "delisted" is automation-only), which is behavior an agent could not infer elsewhere.

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?

Front-loaded with purpose, then examples, then event semantics — a sensible order for a 69-parameter tool. It is long, but most sentences carry load; only the "Legacy listing/event filters remain supported" line and the terse engine-mode sentence feel like filler that could be tightened.

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?

Given 69 parameters, nested objects, and no output schema, the description covers the high-risk gaps: credit spend, outreach/contacts, confirm-before-enable, event firing rules, and the params escape hatch. It leaves less-explained the automation-specific fields like unknown_policy, unknown_list_id, contacts_condition, and outreach_routes ordering, though those carry schema descriptions.

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?

With 86% schema coverage the baseline is 3, but the description adds real meaning: the params={source:"data_search",...} shape, the min_amount/max_amount vs min_price/max_price naming divergence, and worked examples mapping natural language to frequency/day_of_week/week_of_month/timezone. The events taxonomy explanation is essential because the schema enum carries no per-value semantics.

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?

Opens with a specific verb+resource: "Schedule a recurring property search," immediately establishing this as creation of a scheduled automation rather than a one-off search. It further distinguishes the two engine modes (legacy vs data_platform) and names sibling tools (spur_data_search, spur_search_properties) for the adjacent operations.

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?

Gives explicit workflow guidance: run spur_data_search once first so the user can preview, then schedule, and approve settings via confirm before enabling because each run spends credits and can contact people. It also routes filter syntax to spur_search_properties for parity. It stops short of stating when to use this versus the manage/run automation siblings, but the when-to-use context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources