Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

greystar_search

Search Greystar apartment communities by market area, city, state, country, rent range, or free text to find published listings and starting prices.

Instructions

Search Greystar apartment communities. Lists Greystar communities published on greystar.com, optionally filtered by market area, neighborhood, city, state, country, starting rent, or free text. Filter values must come from /greystar/markets; an unknown value returns 400. Starting prices reflect each community's published minimum and are null when none is published. Results come from an hourly snapshot of every community listed on greystar.com; the default order follows the site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoExact city from /greystar/markets
pageNo1-based page
sortNoResult order; relevance keeps the site's own order
queryNoFree-text match on name, address, city, neighborhood, market area, or postal code (max 160 characters)
stateNoState or region abbreviation from /greystar/markets, e.g. TX
per_pageNoResults per page, 1-100
max_priceNoMaximum starting monthly rent; excludes communities with no published price
min_priceNoMinimum starting monthly rent; excludes communities with no published price
market_areaNoExact market area from /greystar/markets, e.g. Greater Austin
country_codeNoISO country code from /greystar/markets, e.g. US
neighborhoodNoExact neighborhood from /greystar/markets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses error behavior (400 on unknown filter value), null semantics for starting prices, and above all that results come from an hourly snapshot, which signals data staleness. It stops short of describing pagination or the shape of a result row.

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 constraints, then data provenance. Sentences are dense and mostly earn their place; the 'default order follows the site' clause is a touch redundant with the sort enum description but still useful context.

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 an 11-parameter search tool with no output schema and no annotations, the description covers source, freshness, filtering constraints, error conditions, and price semantics. An agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema: filter values must be exact values sourced from /greystar/markets, starting rent refers to the community's published minimum, and nulls appear when no price is published. This helps the agent understand min_price/max_price filtering behavior.

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 (Search) and resource (Greystar apartment communities), and pins the scope to 'communities published on greystar.com' with optional filters. An agent can immediately distinguish this from sibling tools like greystar_units or greystar_property.

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?

Explicitly routes the agent to /greystar/markets for valid filter values and warns that unknown values return 400, which is concrete prerequisite guidance. It doesn't contrast against sibling search/property tools with a when-not-to-use clause, so it stops short of a 5.

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

Deploy Server

Other Tools