Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

guardian_headlines

Fetches recent Guardian headlines for a chosen section, defaulting to world, returning titles, URLs, summaries, and publication details.

Instructions

Get Guardian section headlines. Returns recent Guardian headlines for one section. section is optional and defaults to world; the other values are uk-news, us-news, politics, business, technology, environment, science, sport, culture, lifeandstyle and commentisfree. Each item has a title, URL, summary, publication time and author, plus its section when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoGuardian RSS section, defaults to world

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / section / enum
      Added value: +[
+  "world",
+  "uk-news",
+  "us-news",
+  "politics",
+  "business",
+  "technology",
+  "environment",
+  "science",
+  "sport",
+  "culture",
+  "lifeandstyle",
+  "commentisfree"
+]
  2. Addedv1.16.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the returned fields ('title, URL, summary, publication time and author, plus its section'), which is genuinely useful output context, but it says nothing about result count, pagination, freshness window, or ordering for what is implicitly a read/fetch operation.

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?

The first two sentences are tight and front-loaded, stating purpose and scope immediately. The third sentence's full re-enumeration of the section values duplicates the schema and is the only real bloat, keeping it just below a 5.

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?

For a single-parameter, no-annotation tool with no output schema, the definition covers what it does, the default section, and the shape of each returned item, which is close to sufficient. It could be more complete on result volume and pagination, but nothing critical for invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single `section` parameter already has its enum and 'defaults to world' documented in the schema. The description merely repeats that same enum list and default, adding no syntax or semantics beyond the structured field, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Get Guardian section headlines', 'Returns recent Guardian headlines for one section'), so an agent knows exactly what it produces. It does not, however, explicitly differentiate itself from close siblings such as guardian_article or guardian_topic, so it stops short of a 5.

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 implied: call this to retrieve a section's headlines, and `section` selects the section. There is no explicit when-to-use/when-not guidance and no pointer to alternatives like guardian_topic for narrower queries, leaving the agent to infer context.

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