Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

ghanaweb_archive

List paginated canonical article URLs from GhanaWeb archive month sitemaps. First get valid YYYYMM month values from ghanaweb-archive-months.

Instructions

List GhanaWeb archive article URLs. Returns paginated canonical article URLs from one month sitemap. Discover accepted month values from ghanaweb-archive-months; the service only fetches child sitemap URLs derived from that official index.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "month": "<month>"
    },
    "name": "ghanaweb_archive"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default 1)
`limit`	No	Items per page, 1–100 (default 50)
`month`	Yes	A YYYYMM value returned by ghanaweb-archive-months

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.7Oct 1, 2026

TDQS

A4.1/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 it does disclose meaningful behavior: output is paginated, URLs are canonical, the source is a single month's sitemap, and only child sitemap URLs derived from the official index are fetched. It omits error/empty-result behavior and any rate considerations, but the core operational traits are stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences with no filler; the core purpose and the parameter-dependency warning lead. The second sentence ('Returns paginated canonical article URLs from one month sitemap') slightly overlaps the first, keeping it just under fully economical.

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 list tool with no output schema, the description states what is returned (paginated canonical URLs) and where the input values come from. Nothing critical is missing, though it could note behavior on an invalid month.

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 description coverage is 100%, so page, limit, and month are already documented in the schema; baseline 3 applies. The description adds only that month values must come from ghanaweb-archive-months, which is marginal extra meaning beyond the schema text.

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 ('List') plus resource ('GhanaWeb archive article URLs') and scope ('from one month sitemap'). This clearly separates it from siblings like ghanaweb_article, ghanaweb_headlines, and ghanaweb_archive_months without requiring the schema to be opened.

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?

Explicitly directs the agent to ghanaweb-archive-months to discover valid month values and explains the derivation constraint, which is real routing guidance. It stops short of stating when this tool should not be used versus other ghanaweb list/article tools, so it is clear context rather than full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server