Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ghanaweb_article

Extract readable article content and metadata from a GhanaWeb story URL by numeric ID. Returns body paragraphs and public metadata; author names are omitted because JSON-LD lists publisher only.

Instructions

Get GhanaWeb article content. Returns public article metadata and readable body paragraphs. GhanaWeb's JSON-LD identifies the publisher rather than person authors, so authors are omitted.

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": {
      "url": "<url>"
    },
    "name": "ghanaweb_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical GhanaWeb article URL ending in its numeric story ID

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses valuable behavior: returns public article metadata and readable body paragraphs, and proactively explains that authors are omitted because GhanaWeb's JSON-LD identifies the publisher rather than person authors. This prevents an agent from mistakenly expecting author data. It doesn't mention rate limits, caching, or failure modes, but the core behavior is well-disclosed.

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?

Two sentences that are front-loaded and entirely informative. The first sentence states the purpose, the second adds behavioral nuance about author omission. No wasted words.

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 single-URL article retrieval tool with no output schema, the description tells the agent what to pass and what to expect (metadata and body paragraphs, no authors). It could be slightly more complete with a note on error handling or supported URL format, but the core information is present.

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 the schema already documents the sole parameter with a detailed description ('Canonical GhanaWeb article URL ending in its numeric story ID'). The tool description adds no additional parameter semantics. Baseline 3 is appropriate when the schema already handles parameter documentation.

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 article content), plus what is returned ('public article metadata and readable body paragraphs'). This clearly distinguishes it from siblings like ghanaweb_news and ghanaweb_headlines, though it doesn't explicitly name an alternative.

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?

There is no explicit when-to-use guidance or alternatives mentioned. The description does not explain when to pick ghanaweb_article over ghanaweb_news or ghanaweb_headlines. The only contextual clue is the required URL parameter, which is left implicit.

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