Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rollingstone_headlines

Fetch Rolling Stone section headlines by section slug and get each story's title, URL, summary, publication time, and author.

Instructions

Get Rolling Stone section headlines. Returns the latest Rolling Stone stories for one section. section is required and takes one of 34 slugs, including music, music-news, music-album-reviews, politics, tv-movie-reviews, culture and rs-gaming. Each item has its title, URL, summary, publication time and author.

Input Schema

NameRequiredDescriptionDefault
sectionYesRolling Stone section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 full behavioral burden. It helpfully enumerates the returned fields (title, URL, summary, publication time, author), which compensates somewhat for the missing output schema, but it discloses nothing about pagination, result counts, ordering, or rate limits for a list endpoint.

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 qualifiers and return shape. No filler, though the slug examples in sentence three are somewhat redundant with the schema enum.

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 single-param read tool with no output schema, the description covers purpose, the required parameter, and the three or so categories of returned data an agent needs. The main gap is the absence of routing guidance relative to the other rollingstone_* tools in the surface.

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% and the enum already lists all 34 valid slugs, so the schema does the heavy lifting. The description's inline slug examples ('music', 'politics', etc.) merely restate enum values and add no syntax or format detail beyond what the schema provides.

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 and resource ('Get Rolling Stone section headlines') with clarifying scope ('latest Rolling Stone stories for one section'). However, it never distinguishes itself from near-identical siblings like rollingstone_sections, rollingstone_news, or rollingstone_article, which share the Rolling Stone namespace.

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?

Usage is implied by 'for one section' and the required slug, so an agent can infer when to call it. But there is no explicit when-to-use, no exclusions, and no pointer to sibling tools such as rollingstone_sections (to discover valid sections) or rollingstone_article (to read a full story).

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