Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_newsroom_article

Retrieve a Greystar newsroom release by slug to get its title, type, publish date, lead image, and body paragraphs for reporting or archival use.

Instructions

Get a Greystar newsroom release. Retrieves one Greystar newsroom release: title, type (for example Press Release), publish date, lead image, and body paragraphs. Older news stubs carry only a title and date, so the body can be empty. Get slugs from /greystar/newsroom.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesNewsroom slug from /greystar/newsroom

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.3/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 behavioral burden and does disclose a real trait: older news stubs carry only title and date, so the body can be empty, warning the agent against treating empty content as an error. It doesn't cover auth or rate limits, but it adds meaningful context beyond structured data.

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 compact sentences, front-loaded with the verb and resource, followed by return fields and the empty-body caveat, ending with dependency guidance. Every sentence earns its place with no filler.

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?

With no output schema and a single trivial parameter, the description fully covers what comes back and how to obtain the input. Nothing an agent needs to invoke this tool correctly is missing.

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% and the single slug parameter is documented identically in both schema and description. The description's added note that slugs come from /greystar/newsroom reinforces sourcing but adds no syntax beyond what the schema provides, so baseline 3 applies.

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 (Get/Retrieves) and a precise resource (one Greystar newsroom release), and enumerates the returned fields (title, type, publish date, lead image, body). It is clearly distinguishable from the sibling greystar_newsroom, which supplies the listing.

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 tells the agent where to obtain the required slug ('Get slugs from /greystar/newsroom'), routing it to the correct sibling. It does not state any when-not-to-use condition, but for a leaf 'fetch by id' tool the sourcing guidance is the operative instruction.

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