Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_location

Retrieve a Greystar rental hub for a state, city, or neighborhood to get communities, prices, guides, and FAQs. Use slugs from /greystar/locations.

Instructions

Get a Greystar rental hub page. Retrieves one Greystar state, city, or neighborhood rental hub: title, description, editorial guide text as ordered blocks, child locations with summaries, communities listed on the page (id, name, address, and price text when shown), and FAQs. State, city, and neighborhood slugs must come from /greystar/locations; unknown values return 400.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity slug from /greystar/locations
stateYesState slug from /greystar/locations, e.g. tx
neighborhoodNoNeighborhood slug from /greystar/locations; requires city

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose that this is a read ('Get'/'Retrieves'), the exact data returned, and the 400 failure on unknown slugs. It stops short of noting rate limits, caching, or auth requirements, but covers the operation's safety and failure profile well.

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 the core purpose, then a structured enumeration of return fields, then the input constraint. The middle field list is dense but each item earns its place; overall tight and well-ordered with no filler.

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?

No output schema exists, so the description appropriately carries the return-value burden and enumerates the payload honestly. Combined with the slug-sourcing rule and error behavior, an agent has enough to invoke correctly, though it says nothing about page size or pagination.

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 parameters are already self-documented; the description adds the source constraint for all three slugs plus the 400 error consequence, helping the agent avoid invalid input. It does not add format examples beyond the schema's own 'e.g. tx', so it stays modestly above baseline.

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 ('Get a Greystar rental hub page') and enumerates exactly what a hub contains: title, description, editorial guide blocks, child locations, communities with id/name/address/price, and FAQs. An agent can distinguish this page-fetch from sibling entity tools like greystar_property or greystar_markets without opening the schema.

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?

Gives a real prerequisite ('State, city, and neighborhood slugs must come from /greystar/locations') and error behavior ('unknown values return 400'), which is useful procedural context. However, it never states when to choose this hub tool over siblings such as greystar_property, greystar_markets, or greystar_search, 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