Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rawstory_article

Fetch structured Raw Story article content from a canonical rawstory.com URL, including title, authors, publication times, section, image, and body paragraphs.

Instructions

Get Raw Story article content. Returns a Raw Story article by canonical url on rawstory.com, for example https://www.rawstory.com/trump-media-ban-2677933730/: title, description, publication and update times, section, authors, image and body paragraphs (embedded videos excluded). section is omitted for slug-only URLs. Hub, tag and author URLs return an invalid-params error; a missing story returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Raw Story article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 so well: it enumerates returned fields, notes embedded videos are excluded, flags that section is omitted for slug-only URLs, and documents two failure modes (invalid-params, not-found). Auth/rate-limit behavior is not covered, but for a public read tool the disclosure is above average.

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?

Front-loaded with the purpose, then return contents, then edge/error cases. Dense but every clause adds information; it reads as one long paragraph rather than being broken up, which slightly hurts scannability.

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?

No output schema exists, so the description must describe returns and it does fully (title, description, times, section, authors, image, body paragraphs). Combined with the documented error cases and the slug-only edge case, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description goes beyond the schema's terse 'Canonical Raw Story article URL' by giving a concrete example URL and clarifying that hub/tag/author URLs are not valid inputs, which sharpens what 'canonical' means.

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 and resource ('Get Raw Story article content') and pins the exact input ('by canonical url on rawstory.com') with a concrete example. It distinguishes itself from the sibling rawstory_headlines/rawstory_news/rawstory_author/rawstory_sections tools by enumerating what it returns and by explicitly rejecting hub/tag/author URLs.

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?

Gives clear context for when to use it (canonical article URLs) and states the when-not case ('Hub, tag and author URLs return an invalid-params error'). It stops short of naming sibling tools like rawstory_headlines for the non-article cases, so routing is implied rather than explicit.

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