Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

gmanews_headlines

Fetch up to 15 recent GMA News Online headlines for a specified section slug, returning titles, URLs, summaries, timestamps, and images.

Instructions

Get GMA News section headlines. Returns up to 15 of the newest GMA News Online stories for one section, newest first. section is required and takes one of 44 slugs such as topstories-world, money-economy, sports-nba or showbiz. Each item has title, url, summary, published_at (UTC) and image_url. Quiet sections can return only a few items. An invalid or missing section returns 400.

Input Schema

NameRequiredDescriptionDefault
sectionYesGMA News section slug

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 full burden and does well: it discloses the 15-item cap, newest-first ordering, that quiet sections may return few items, the per-item fields, and that an invalid or missing section returns 400. It stops short of auth/rate-limit details, but the truncation and error behavior are exactly the traits an agent needs.

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?

Front-loaded purpose, then return shape, then parameter, then caveats and error behavior. Every sentence conveys distinct information and none is padding.

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 correctly enumerates the returned item fields (title, url, summary, published_at UTC, image_url). Combined with the item count, ordering, and error semantics, an agent has everything needed to call and interpret this tool.

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% (the enum fully enumerates all 44 slugs), so the baseline is 3. The description adds value by labeling the values as 'slugs', giving representative examples, stating the count of 44, and tying the parameter to the 400 error path — going modestly beyond the 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 GMA News section headlines') and immediately scopes it to 'one section' with a bounded result set, which distinguishes it from article/news/sections siblings. An agent can tell this is the section-level headline feed 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?

Usage is implied: it's clear you call this to get headlines for a section, and the required `section` plus the 400-on-invalid note constrains it. But there is no explicit when-to-use/when-not guidance and no named alternative (e.g. gmanews_news or gmanews_article) to route between, leaving the sibling choice to inference.

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