Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gulfnews_headlines

Retrieve current Gulf News headlines by required section slug; each result includes the article title and canonical URL.

Instructions

Get Gulf News section headlines. Returns current Gulf News headlines for one section. section is required and takes one of 19 slugs such as latest-news, business, uae, sport, living-in-uae or your-money; other values return an invalid-params error. Each item has a title and canonical article URL.

Input Schema

NameRequiredDescriptionDefault
sectionYesGulf News section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 burden. It does disclose real behavioral traits beyond the schema: that invalid section values produce an invalid-params error, and that each result item contains a title and canonical article URL. It omits auth/permission or rate-limit behavior, but for a simple read tool this is solid disclosure.

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?

Three sentences, front-loaded with the core action, then the constraint and the error case, then the return shape. No filler or repetition of the tool name.

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?

With no output schema, the description compensates by describing return fields (title and canonical article URL), and it covers the single required parameter and its failure mode. Nothing needed to invoke the tool correctly is missing.

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 already lists all values, so the baseline is 3. The description adds value by citing representative slug examples and explicitly documenting the invalid-params failure mode for non-enum values, which the schema does not express.

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 Gulf News section headlines') plus the scope ('for one section'). This clearly separates it from gulfnews_news, gulfnews_sections, and gulfnews_article without needing 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?

The description implies usage (fetch headlines for a single selected section) but never names alternatives such as gulfnews_news or gulfnews_sections, nor states when-not to use it. Guidance is inferred rather than explicit.

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