Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_locations

List Greystar rental hub locations by state, city, or neighborhood, returning slugs and URLs for use with location detail endpoints.

Instructions

List Greystar rental hub locations. Lists Greystar's state, city, and neighborhood rental hub pages (the site's own location tree) with slugs and URLs. Use the slugs with /greystar/location for a hub's editorial content, child locations, listed communities, and FAQs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug from this list; requires state
pageNo1-based page
levelNoHub level
stateNoState slug from this list, e.g. tx
per_pageNoEntries per page, 1-200

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the result is a location tree of slugs and URLs, but says nothing about pagination behavior (page/per_page exist in the schema), rate limits, or whether this is a static sitemap-style tree.

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 with zero filler, and the core purpose is front-loaded before the cross-tool routing hint.

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 no output schema, the description does the work of explaining what is returned (slugs and URLs of the location tree), so the agent knows the shape of results. It omits pagination semantics, but the schema's page/per_page and the 100% param coverage offset that gap.

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 baseline is 3. The description reinforces that the returned values are slugs usable as inputs elsewhere, but adds no format or syntax detail beyond what the schema already documents for city/state/level.

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+resource ('List Greystar rental hub locations') and then clarifies exactly what the entries are — state, city, and neighborhood hub pages with slugs and URLs. This distinguishes it clearly from the sibling greystar_location, which serves editorial content for a single hub.

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: 'Use the slugs with /greystar/location for a hub's editorial content, child locations, listed communities, and FAQs.' This names the alternative tool and the condition that selects it, though it doesn't state when this list tool itself should be avoided.

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