Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rappler_sections

Get all 175 Rappler categories with live feeds for headlines, including news-updates, business, nation, fact-check, and climate-change. Each includes slug, name, and URL.

Instructions

Get Rappler sections. Lists the 175 Rappler categories that have a live feed and are accepted by rappler-headlines, such as news-updates, business, nation, fact-check and climate-change. Each entry has a slug, a display name and the category url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 reasonably well: it discloses that only categories 'that have a live feed' are returned (a filtering rule) and that each entry carries a slug, name and url. It does not state auth requirements or whether the list is cached/static, but for a parameterless read-only listing this is solid disclosure.

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?

Three sentences, front-loaded with the action and count, then concrete examples, then the entry shape. No filler and every clause adds information.

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?

For a no-param, no-annotation, no-output-schema tool, the description supplies everything needed: what it lists, how many, example values, and the fields of each result. Nothing material is missing.

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. The description instead describes the shape of each returned entry (slug, name, url), which is useful since there is no output schema.

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 Rappler sections'), then sharpens it by naming the exact count (175), giving example slugs, and describing each entry's fields. The tie to `rappler-headlines` makes it distinguishable from the other rappler_* siblings without opening any schema.

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 explains the workflow role by noting the categories 'are accepted by `rappler-headlines`', which tells the agent why to call this before fetching headlines. There is no explicit when-not guidance or named alternative, but the consuming tool is made 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