Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

khaleejtimes_headlines

Fetch Khaleej Times headlines for any section or sub-section by passing its slug, such as business-markets, to get titles, URLs and publication times.

Instructions

Get Khaleej Times section headlines. Returns current Khaleej Times headlines for one section or sub-section. section is required; its slug is the section's URL path with slashes turned into hyphens, so /business/markets is business-markets. Top-level sections mix their sub-sections' stories. Each item has its title, URL and publication time, plus summary, author and image when the outlet provides them. Call khaleejtimes-sections for the slugs.

Input Schema

NameRequiredDescriptionDefault
sectionYesKhaleej Times section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that top-level sections mix sub-sections' stories, and describes the return shape (title, URL, publication time, optional summary/author/image). It omits auth/caching/rate-limit behavior, so not a 5.

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?

Well front-loaded: purpose first, then slug rule, then hierarchy note, then return shape, then the sibling pointer. Each sentence adds distinct information with no padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description compensates by enumerating returned fields. Combined with the slug rule and required-parameter note, an agent has everything needed to call the tool correctly.

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% and the enum lists valid slugs, so baseline would be 3. The description adds genuine value by explaining the slug derivation rule (URL path with slashes replaced by hyphens, e.g. `/business/markets` → `business-markets`), which the enum alone 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 (Get) and resource (Khaleej Times section headlines) with scope ('one section or sub-section'). An agent can distinguish it from siblings like khaleejtimes_news and khaleejtimes_article.

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 states `section` is required and routes the agent to `khaleejtimes-sections` for slug values. It gives no when-not-to-use guidance or comparison against sibling tools, but the prerequisite routing is clearly valuable.

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