Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_units

Search available Greystar apartment units by location, bedrooms, bathrooms, price, and community highlights. Returns matching units grouped by community with addresses and lease terms.

Instructions

Search available Greystar apartment units. Searches apartment units currently available to rent on greystar.com within one location (nationwide by default), filtered by bedrooms, bathrooms, building type, community highlights, and monthly price, sorted by relevance or price. Results are grouped by community: each carries its address, coordinates, the number of matching units, and up to about 100 units with unit number, floor plan, bedrooms, bathrooms, price range, and lease term. The response also returns filter counts for the location. Several values of one filter match any of them. Get location values from /greystar/unit-locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page
sortNoResult order
bedroomsNoBedroom count; repeat for several (0 is studio)
locationNoSearch location slug from /greystar/unit-locations, e.g. austin-tx, texas or greater-austin/round-rock
per_pageNoCommunities per page, 1-100
bathroomsNoBathroom count; repeat for several
max_priceNoMaximum monthly unit price
min_priceNoMinimum monthly unit price
highlightsNoCommunity highlight; repeat for several (matches any)
building_typeNoBuilding type; repeat for several

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/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 so well: it discloses the nationwide default, the grouping-by-community result model, the ~100-unit cap per community, and the OR semantics of multi-value filters ("Several values of one filter match any of them"). Only auth/rate-limit context is absent, which is minor for a read search.

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?

Purpose is front-loaded and each subsequent sentence adds distinct information (filters, sort, result shape, filter-count behavior, location prerequisite). It is slightly dense but no sentence is wasted.

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 10-parameter search tool with no output schema, the description compensates fully by describing the grouped return structure (address, coordinates, unit count, unit fields, lease term) and the filter-count response. An agent has everything needed to call it and interpret results.

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 coverage is 100%, so the schema already documents all ten parameters and their enums; baseline 3 applies. The description adds a modest amount of meaning by noting the multi-value OR behavior and the sort options (relevance or price), but largely repeats the filter list already present in the schema.

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 opens with a specific verb+resource ("Search available Greystar apartment units") and scopes it to greystar.com inventory, filtered by named facets. It is clearly distinguishable from sibling tools like greystar_locations or greystar_property, though it never explicitly names which sibling to use for what.

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?

It supplies a concrete prerequisite — "Get location values from /greystar/unit-locations" — and states the default scope (nationwide). However, it gives no explicit when-to-use/when-not guidance or contrast with the other greystar search/listing siblings, leaving alternative selection to inference.

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