Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gbnews_article

Extract a GB News article's title, authors, timestamps, lead image, and body paragraphs from its gbnews.com URL; returns structured JSON for news, opinion, and sport stories.

Instructions

Get GB News article content. Returns one GB News story by its gbnews.com url (news, opinion or sport; query strings are ignored). The response has the title, description, publish and update times, section label, authors, lead image and body paragraphs, without captions or widgets. paywalled is never set. Video, audio, author and hub pages return an error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical GB News story URL

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 full burden and does it well: it enumerates the returned fields, states what is excluded (captions, widgets), clarifies that `paywalled` is never set, and lists the page types that error out. Missing only operational details like rate limits or auth requirements.

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?

Front-loaded with the core purpose in the first sentence, then progressively adds scope, return contents, and failure modes. Three tight sentences with no filler; every clause carries information.

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, so the description must describe return values, and it does so comprehensively (title, description, publish/update times, section label, authors, lead image, paragraphs). Combined with error conditions and URL constraints, nothing an agent needs to call it 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%, so the baseline is 3, but the description adds real meaning beyond the schema's 'Canonical GB News story URL' by specifying the `gbnews.com` domain requirement and that query strings are ignored.

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?

Specific verb+resource ('Get GB News article content') that clearly distinguishes this single-story fetch from siblings like gbnews_headlines, gbnews_news, and gbnews_sections. An agent knows this returns one article by URL rather than a list or section feed.

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?

Explicit about which URL types work (news, opinion, sport) and which fail (video, audio, author, hub pages), plus the note that query strings are ignored. It stops short of naming the sibling tools to use for author/hub content, so it's clear context without full alternative routing.

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