Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

khaleejtimes_article

Retrieve Khaleej Times article content by submitting a canonical article URL. Returns metadata and body paragraphs in clean JSON, including timestamped headlines for live-blog pages.

Instructions

Get Khaleej Times article content. Returns public Khaleej Times article metadata and body paragraphs from a canonical article URL. Live-blog pages are accepted and return their timestamped update headlines as paragraphs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Khaleej Times article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden. It discloses that the tool returns public article metadata and body paragraphs, and it explicitly documents the special live-blog behavior of converting timestamped updates into paragraphs. This adds real value beyond the schema.

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, each earning its place. The main action and output are front-loaded, and the live-blog caveat is appended compactly without redundancy.

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-parameter read-only article fetcher, the description is suitably complete: it states the input type, the output content, and the special live-blog case. It could be slightly stronger with an example URL or an explicit note about the return shape, but with no output schema the stated return of metadata and paragraphs is sufficient.

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 url parameter. The description reinforces that the URL must be canonical and that live-blog URLs are valid inputs, but it does not add substantial semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses a specific verb-resource pairing: "Get Khaleej Times article content" from a canonical article URL. It precisely distinguishes this tool from sibling khaleejtimes_headlines, khaleejtimes_news, khaleejtimes_sections, and khaleejtimes_author by indicating it retrieves full article content rather than lists or author info.

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?

The description gives clear context: use this tool with a canonical Khaleej Times article URL, and live-blog URLs are also accepted. It does not explicitly name alternatives or state when not to use it, but for a single-URL article fetcher the usage context is clear enough.

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