Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghanaweb_headlines

Fetch GhanaWeb section headlines by slug to retrieve article card titles, URLs, and image URLs for news, sports, business, and other GhanaWeb sections.

Instructions

Get GhanaWeb section headlines. Returns the article cards currently listed on one GhanaWeb section. section is required and takes one of 15 slugs such as news, sports, crime, tabloid or regional. Each item has its title, url and, when the card shows one, image_url. Summary, author and publication time are not returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug from ghanaweb-sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/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 return shape (title, url, optional image_url) and explicitly states what is NOT returned (summary, author, publication time). It stops short of pagination or rate-limit behavior, but the return-field disclosure is genuinely useful.

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 tight sentences, front-loaded with the core action, then the parameter, then the return shape. No filler, and the negative-return note earns its place.

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 read-only, single-parameter list tool with no output schema, the description covers purpose, parameter source, and return fields sufficiently. Only pagination/volume expectations are unaddressed, a minor gap given the tool's simplicity.

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% and the enum already lists all 15 slugs plus a description pointing to ghanaweb-sections. The description repeats example slugs (news, sports, crime, tabloid, regional) already present in the enum, adding only marginal value beyond the schema.

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 (Get) and resource (GhanaWeb section headlines) with clear scope (one section). It is distinguishable from single-item siblings like ghanaweb_article and archive tools, though it does not explicitly separate itself from ghanaweb_news or ghanaweb_sections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (fetch headlines for a given section) but offers no when-to-use guidance, no when-not-to-use, and no named alternatives among the many ghanaweb_* siblings such as ghanaweb_news or ghanaweb_sections.

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