Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

globalnews_article

Fetch a Global News article from its canonical globalnews.ca URL and return structured data: title, description, authors, publish/update times, body paragraphs, and paywall flag.

Instructions

Get Global News article content. Returns one Global News article by url, a canonical globalnews.ca link of the form /news/<id>/<slug>/ or /the-curator/<id>/<slug>/. The response has the title, description, section, authors, lead image, publish and update times, the body as paragraphs, and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Global News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations the description carries the full burden. It usefully discloses the `paywalled` flag and the response shape, but says nothing about error behavior for non-canonical URLs, permission/auth needs, or rate limits, leaving real behavioral gaps.

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 tight sentences, front-loaded with purpose, then parameter shape, then response contents. Every sentence adds information an agent needs and none is redundant.

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?

No output schema exists, so the description must summarize returns, and it does so thoroughly (title, description, section, authors, image, times, paragraphs, paywall). Only error/auth behavior is missing, which is minor for a single-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 exceeds it by specifying the accepted canonical forms (`/news/<id>/<slug>/` and `/the-curator/<id>/<slug>/`), which meaningfully constrains what a valid `url` looks like.

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?

States a specific verb ('Get') and resource ('Global News article content') and clarifies it returns exactly ONE article by url, which distinguishes it from the list-oriented siblings (globalnews_headlines, globalnews_news). It does not explicitly name a sibling alternative, so it falls just short of the top tier.

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?

Usage is only implied: the agent infers it should call this once it holds a canonical article URL. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as headlines/news/sections tools.

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