Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rappler_author

Fetch a Rappler author profile by slug or canonical URL to retrieve their name, bio, social links, and 10 most recent articles.

Instructions

Get a Rappler author profile. Returns a Rappler author's profile, looked up by slug (for example delfin-dioquino) or by canonical url; exactly one is required. The response has the name, bio, social_links and the 10 most recent articles, each with title, URL, section and publication time. There is no further paging. bio and social_links are omitted when empty; an unknown author returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical rappler.com/author/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. delfin-dioquino

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the returned fields, that there is no further paging, that bio and social_links are omitted when empty, and that an unknown author returns not-found. It does not mention auth or rate limits, but read-only behavior and failure handling are clear.

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?

Four compact sentences, front-loaded with purpose and lookup rules, then response shape and edge cases. No filler.

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 read-only lookup tool with no output schema or annotations, the description covers lookup inputs, required-one-of constraint, response fields, paging limits, empty-field omission, and not-found behavior. Nothing essential 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?

Schema coverage is 100%, so the baseline is 3, but the description adds a meaningful constraint not captured by the schema: exactly one of slug or url is required, despite both being optional in the schema. It also gives a concrete slug example and calls url canonical.

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 a Rappler author profile, with the lookup keys and returned content identified. An agent can distinguish it from Rappler article/news/section tools without opening the schema.

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?

Explains that exactly one of slug or url is required and names both lookup modes, but does not explicitly say when to use this tool versus sibling author/article tools or when slug should be preferred over url.

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