Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gulfnews_article

Extract structured content from a canonical gulfnews.com article URL, including title, authors, images, times, and body paragraphs for research or summaries.

Instructions

Get Gulf News article content. Returns a Gulf News article by url, a canonical gulfnews.com link whose path ends in the -1.<id> suffix. The response has the title, description, section, authors, lead image, publish and update times, and body paragraphs. Section and author pages are rejected, and paywalled is omitted because sampled articles were freely readable.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Gulf News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 burden and does disclose the return shape (title, description, section, authors, lead image, times, body paragraphs) plus two non-obvious traits: rejection of section/author pages and the deliberate omission of the `paywalled` field. Auth requirements and rate limits are not mentioned, but for a read-only article fetch the key behavior is covered.

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?

Four tight sentences, front-loaded with the core purpose before the output fields and edge cases. Every sentence carries information; nothing is filler. Slightly dense but appropriate for the amount of behavior it must convey.

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?

Because there is no output schema and no annotations, the description must cover both return contents and behavioral edges, and it does: fields returned, invalid input types, and the paywalled omission. An agent has enough to invoke this correctly; only auth/error-mode detail is absent, which is minor for a public article fetch.

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%, so the baseline is 3, but the description goes beyond the schema's generic "Canonical Gulf News article URL" by specifying the path must end in the `-1.<id>` suffix and that section/author pages are invalid. That extra constraint meaningfully reduces malformed calls.

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?

"Get Gulf News article content" states a specific verb and resource, and the elaboration about canonical URLs ending in `-1.<id>` pins down exactly what entity is fetched. It doesn't explicitly contrast itself with siblings like gulfnews_headlines or gulfnews_sections, but the name plus the URL-shape detail make the target unambiguous.

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 real usage constraints: the URL must be a canonical gulfnews.com link ending in the `-1.<id>` suffix, and section/author pages are rejected. That tells the agent when the call will succeed and when it will fail, though it names no alternative tool for finding valid article URLs.

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