Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

aljazeera_article

Fetch Al Jazeera article content from a canonical URL, returning title, authors, dates, section, lead image, and body paragraphs for reading, research, or summaries.

Instructions

Get Al Jazeera article content. Returns an Al Jazeera article by url, a canonical dated www.aljazeera.com address such as /news/2026/9/20/example-slug: title, description, publication and update times, section, credited authors, lead image and body paragraphs. Live-blog URLs return their opening summary bullets as the body; a video page with no article text returns 503 and a malformed URL 400.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.aljazeera.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 behavioral burden and does well: it discloses that live-blog URLs return opening summary bullets as the body, and that video pages yield HTTP 503 while malformed URLs yield 400. These edge-case/error behaviors are genuinely useful and beyond what the schema offers, though auth/rate-limit context is absent.

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?

Front-loaded with the core action, followed by return fields and then edge cases. The single dense paragraph with a colon list is efficient though slightly run-on; every clause carries information.

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 one-parameter tool with no annotations and no output schema, the description usefully enumerates return fields and error behaviors, making it callable without inspecting anything else. Missing only auth/permission context, which keeps it short of a 5.

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% (baseline 3), but the description goes further by giving a concrete canonical path example and tying malformed input to a 400 response, adding format meaning the bare schema string does not convey.

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 Al Jazeera article content") and enumerates exactly what is returned (title, description, times, section, authors, lead image, body paragraphs). The 'article' scope is clearly distinct from sibling headline/topic/category tools, so an agent can separate it 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 by the required canonical URL and the format hint ("a canonical dated www.aljazeera.com address such as /news/2026/9/20/example-slug"), which tells the agent what input is acceptable. However, there is no explicit when-to-use/when-not guidance and no sibling (e.g. aljazeera_headlines for discovery) is named as an alternative.

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