The Guardian

Search

search

Read-onlyIdempotent

Search The Guardian newspaper archive (UK-based international news outlet) for articles by keyword, section, tag, or date range. Returns headlines with author, section, publication date, web URL, and optional full body text. Use for "Guardian coverage of X" or UK/EU-perspective news on world events.

Input Schema

Name	Required	Description	Default
`q`	No
`tag`	No
`page`	No
`section`	No
`to_date`	No
`order_by`	No
`from_date`	No
`page_size`	No
`show_tags`	No
`show_fields`	No
`show_elements`	No

Output Schema

Name	Required	Description	Default
`response`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "page_size": 10,
+    "q": "climate change",
+    "section": "environment"
+  },
+  {
+    "from_date": "2024-01-01",
+    "order_by": "newest",
+    "page": 1,
+    "q": "artificial intelligence",
+    "show_fields": "byline,standfirst",
+    "to_date": "2024-12-31"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Content search results from The Guardian",
+  "properties": {
+    "response": {
+      "properties": {
+        "currentPage": {
+          "description": "Current page number",
+          "type": "number"
+        },
+        "pageSize": {
+          "description": "Number of results per page",
+          "type": "number"
+        },
+        "pages": {
+          "description": "Total number of pages",
+          "type": "number"
+        },
+        "results": {
+          "description": "Array of article results",
+          "items": {
+            "properties": {
+              "apiUrl": {
+                "description": "API endpoint for this article",
+                "type": "string"
+              },
+              "fields": {
+                "description": "Additional fields if requested",
+                "type": "object"
+              },
+              "id": {
+                "description": "Article ID",
+                "type": "string"
+              },
+              "sectionId": {
+                "description": "Section ID",
+                "type": "string"
+              },
+              "sectionName": {
+                "description": "Section name",
+                "type": "string"
+              },
+              "tags": {
+                "description": "Associated tags if requested",
+                "items": {
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "type": {
+                "description": "Content type",
+                "type": "string"
+              },
+              "webPublicationDate": {
+                "description": "Web publication date ISO string",
+                "type": "string"
+              },
+              "webTitle": {
+                "description": "Article web title",
+                "type": "string"
+              },
+              "webUrl": {
+                "description": "Article web URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "startIndex": {
+          "description": "Start index of current page",
+          "type": "number"
+        },
+        "status": {
+          "description": "Response status",
+          "type": "string"
+        },
+        "total": {
+          "description": "Total number of results",
+          "type": "number"
+        },
+        "userTier": {
+          "description": "User tier level",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds context about the source being a UK newspaper and optional full body text, but no behavioral details beyond what annotations cover. No contradiction.

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?

Two sentences: first states purpose and outputs, second provides usage guidance. No wasted words, front-loaded with critical information.

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?

Given complex schema (11 params), presence of output schema, and detailed annotations, the description gives a solid high-level understanding. It covers the main filters and return fields, though it does not enumerate every parameter. The output schema handles detailed return structure, so this is sufficient.

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 has 11 parameters with 0% description coverage. The description mentions key filters like keyword, section, tag, date range, and notes optional full body text. However, many parameters (e.g., page, page_size, show_tags, show_elements) are not explained. The examples partially compensate, but overall the description adds moderate value beyond obvious parameter names.

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?

The description clearly states 'Search The Guardian newspaper archive... for articles by keyword, section, tag, or date range. Returns headlines with author, section, publication date, web URL, and optional full body text.' This provides a specific verb (search), resource (Guardian archive), and outputs, distinguishing it from sibling tools like 'search_within' or general news tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises 'Use for "Guardian coverage of X" or UK/EU-perspective news on world events.' This gives clear context for when to choose this tool over siblings, and implies it is not for non-Guardian or non-UK/EU news.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Guardian tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.