Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

greystar_article

Retrieve a Greystar renter guide or blog post by section and slug, returning title, metadata, lead image, and structured body blocks.

Instructions

Get a Greystar renter guide or blog post. Retrieves one Greystar renter guide or blog post: title, description, category, publish date (blog posts), lead image, and the body as ordered heading, paragraph, and list blocks. Get section and slug values from /greystar/articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesArticle slug from /greystar/articles
sectionYesContent section

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?

No annotations are provided, so the description carries the behavioral burden. It discloses the returned content shape (title, description, category, publish date, lead image, plus body as ordered heading/paragraph/list blocks), which is useful for a read operation, but says nothing about auth, pagination, or failure behavior for a missing slug.

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?

Three tight sentences with no filler, front-loading what the tool returns before the input-sourcing note. Nothing wastes space, though the return-field enumeration is a touch list-like.

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 usefully compensates by enumerating the returned fields. For a simple two-parameter read tool this is close to complete, with only error/auth behavior left undocumented.

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 schema already documents both params, including that slug comes from /greystar/articles. The description's sourcing note largely restates the schema, so it adds little beyond the baseline.

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 (Get/Retrieves) and resource (one Greystar renter guide or blog post), and the singular 'one' plus the required section+slug params distinguishes it from the greystar_articles listing sibling. It doesn't name the sibling explicitly, but the single-item resource is unambiguous.

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?

It tells the agent where to obtain its inputs ('Get section and slug values from /greystar/articles'), which effectively routes the agent to the companion listing tool. There is no explicit when-not or exclusion, but the retrieval context is clear.

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