Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

clevelandcom_news

Fetch Cleveland.com top stories from a 50-item public RSS feed for quick news monitoring. Returns publisher teaser summaries, not full article text.

Instructions

Get Cleveland.com top stories. Returns Cleveland.com's 50-item public top-stories RSS feed. Summaries and encoded content are publisher teasers; this endpoint does not claim to return full article text. Editorial section inventory and article pages could not be reliably verified due to upstream DataDome blocking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

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 full burden and does well: it discloses the feed's fixed 50-item size, warns that summaries and encoded content are publisher teasers rather than full article text, and admits that section inventory and article pages could not be verified due to upstream DataDome blocking. It omits auth/rate-limit details, but the 'what you actually get' caveat is exactly the kind of context annotations would otherwise need to supply.

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, front-loaded with the core purpose before the caveats. Each sentence adds distinct value (purpose, payload, limitations), though the final sentence about DataDome is somewhat defensive and could be folded more crisply.

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 parameterless tool with no output schema, the description covers what is returned, how much of it, and the fidelity limits of the content. Nothing an agent needs to invoke it correctly is missing, though it does not describe item fields or ordering.

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?

The tool takes zero parameters, so the baseline is 4. No parameter semantics are needed, and the description correctly does not invent any.

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') and resource (Cleveland.com top stories) and pins down the exact payload: a public 50-item top-stories RSS feed. An agent can distinguish this from the many sibling news feeds by publisher and content shape.

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 usage (fetch current Cleveland.com headlines) and scopes the result set, but never says when to choose it over siblings or what to do if the agent needs article text or section listings. Usage is inferred from scope, not 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