Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_articles

List renter guides and blog posts from Greystar's public sitemap, newest first, with section, slug, URL, and last-modified date; fetch full article details by section and slug.

Instructions

List Greystar renter guides and blog posts. Lists Greystar's renter guides (applying and leasing, general guides, moving) and blog posts from its public sitemap, newest first. Entries carry the section, slug, URL and last-modified date; fetch /greystar/articles/{section}/{slug} for the title and body.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page
queryNoText matched against the slug
sectionNoContent section
per_pageNoEntries per page, 1-100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the data source (public sitemap), sort order (newest first), and the fields each entry carries (section, slug, URL, last-modified), which is useful. However it says nothing about pagination behavior, rate limits, or whether the list is complete, leaving notable gaps for a read tool.

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?

Two tight sentences with the core purpose front-loaded and the return-shape/detail-fetch info appended. No filler; every clause earns its place.

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?

For a list tool with no output schema, the description reasonably conveys what entries contain and how to get full content. Minor gaps remain around pagination behavior and result limits, but the essentials an agent needs are present.

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 four parameters including the section enum. The description reinforces the section taxonomy but adds no new syntax or semantics for query, page, or per_page beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific verb (List) and resource (Greystar renter guides and blog posts), and enumerates the sections covered, so the agent knows exactly what this returns. It does not explicitly name a sibling tool, but the mention of fetching /greystar/articles/{section}/{slug} implicitly points to the detail operation.

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?

The description implies a two-step workflow (list here, then fetch the article path for title/body) and notes ordering as newest first, but it gives no explicit when-to-use vs. alternatives or exclusions. Usage is inferred rather than stated.

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