Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rappler_headlines

Retrieve the latest headlines from a specific Rappler section by providing its category slug, returning each story's title, URL, summary, and author.

Instructions

Get Rappler section headlines. Returns the latest Rappler stories for one section. section is required and takes one of the site's category slugs, such as business, nation, entertainment, fact-check, investigative or climate-change. Each item has its title, URL, summary, publication time and author, plus an image when the outlet provides one.

Input Schema

NameRequiredDescriptionDefault
sectionYesRappler section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does add useful behavior: it says results are the latest stories for one section and lists returned fields including title, URL, summary, publication time, author, and image. It does not mention result count, pagination, ordering beyond 'latest', authentication, or rate limits.

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?

The definition is three tight sentences, front-loaded with the purpose, followed by the parameter requirement and return fields. Every sentence contributes useful information without repetition.

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 simple one-parameter read-only tool with no output schema, the description explains the input domain and the shape of returned items. It is nearly complete, though it could state whether pagination or a result limit applies.

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%, so the enum and required flag already document `section`; the description adds that it is a site category slug and provides representative examples. That is helpful but does not add much beyond the schema's existing enum and description.

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?

The description states a specific verb and resource: 'Get Rappler section headlines' and 'Returns the latest Rappler stories for one section.' It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as rappler_sections or rappler_news.

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 the phrase 'for one section' and by the required `section` slug, with examples of valid categories. However, it gives no explicit when-to-use guidance, exclusions, or direction to a sibling such as rappler_sections for discovering slugs.

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