Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_newsroom

List Greystar corporate newsroom releases and articles from its public sitemap, newest first, with slug, URL, and last-modified date. Fetch individual releases for title, date, and body.

Instructions

List Greystar newsroom releases. Lists Greystar corporate newsroom releases and news articles from its public sitemap, newest first, with slug, URL and last-modified date. Fetch /greystar/newsroom/{slug} for the title, date, and body.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does well: it discloses the source (public sitemap), the ordering (newest first), and the returned fields (slug, URL, last-modified date), plus the follow-up fetch pattern. It stops short of noting rate limits or pagination behavior.

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; the core purpose and the follow-up fetch instruction are front-loaded and easy to parse.

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?

There is no output schema, so the description usefully enumerates the returned fields and ordering, and explains the two-step workflow to get titles/dates/bodies. It is close to complete, with only pagination/rate behavior unaddressed.

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 schema already documents page, query (matched against slug), and per_page. The description adds no further parameter meaning, making the baseline 3 appropriate.

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 (List) and resource (Greystar newsroom releases / corporate news articles) and clarifies the data source (public sitemap). It implicitly distinguishes itself from the sibling greystar_newsroom_article by explaining that the detail fetch is a separate step.

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?

Provides clear routing: this tool lists slugs/URLs/dates, and the agent should then 'Fetch /greystar/newsroom/{slug}' for full content. It does not explicitly contrast with greystar_articles or greystar_search, but the intended workflow is evident.

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