NewsMCP

get_story

Read-only

Expand one story: full summary, classification, actors, and source links.

Use this after any search, when the user wants more than the digest line for a particular story. It is the only tool that can return a story's complete source list.

Input Schema

Name	Required	Description	Default
`event_id`	Yes	The `event_id` of a story from an earlier result (e.g. `evt_...`). A story folded into a more complete one answers 404 naming its replacement id — fetch that instead.
`include_sources`	No	False (default) returns a sample of source links; True returns every one. A large story can carry several hundred, so leave this off unless the user asked for the full list. This is the only place the complete list is available — the search endpoints cap it.
`response_format`	No	markdown (default), text, or json. Pass the format the user asked for rather than reformatting afterwards.	markdown

Output Schema

Name	Required	Description
`size`	No	Article count.
`sector`	No
`reports`	No
`sources`	No	Source article URLs — a sample or the full list per verbosity.
`abstract`	No
`entities`	No	Key actors named in the story.
`event_id`	No	Stable id, e.g. evt_...
`headline`	No
`last_seen`	No	ISO 8601 UTC.
`newsrooms`	No	Independent newsrooms — the corroboration signal.
`one_liner`	No
`event_type`	No	family.leaf taxonomy value, e.g. deals.merger_acquisition.
`first_seen`	No	ISO 8601 UTC.
`content_type`	No
`source_count`	No	Publisher domains, mirrors included.
`language_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

removedInput schema / properties / api_key

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional NewsMCP API key for this call; forwarded upstream as x-api-key. Only one request may be in flight at a time, so never call in parallel."
-}

removedInput schema / properties / llm_model

Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

Changed1 schema field changedSep 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "One synthesized news event, expanded.",
+  "properties": {
+    "abstract": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "content_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "entities": {
+      "description": "Key actors named in the story.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "name": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "event_id": {
+      "description": "Stable id, e.g. evt_...",
+      "type": "string"
+    },
+    "event_type": {
+      "description": "family.leaf taxonomy value, e.g. deals.merger_acquisition.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "first_seen": {
+      "description": "ISO 8601 UTC.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "headline": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "language_count": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "last_seen": {
+      "description": "ISO 8601 UTC.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "newsrooms": {
+      "description": "Independent newsrooms — the corroboration signal.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "one_liner": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reports": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "sector": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "size": {
+      "description": "Article count.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "source_count": {
+      "description": "Publisher domains, mirrors included.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "sources": {
+      "description": "Source article URLs — a sample or the full list per verbosity.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely new behavioral context: this is the only route to a complete source list because search endpoints cap it, and that source volume can reach several hundred links.

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?

Three short sentences with the core action front-loaded and the usage cue immediately after. The 'only place the complete list is available' claim is repeated between prose and schema, which is mild duplication rather than harmful, but it does cost a bit of tightness.

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?

With an output schema present, return-value detail is unnecessary, and the description still covers the expansion scope, the source-list caveat, and the post-search workflow. Nothing essential for correct invocation is missing, though naming the search sibling would have closed the last gap.

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%, so all three parameters are already documented in the schema, including the include_sources trade-off and the 404-replacement behavior for event_id. The description adds nothing beyond what the schema states, so the baseline of 3 applies.

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?

States a specific verb and resource ('Expand one story') and enumerates what comes back: full summary, classification, actors, source links. It also claims a unique capability ('the only tool that can return a story's complete source list'), which separates it from news and the check_* siblings.

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?

'Use this after any search, when the user wants more than the digest line for a particular story' gives a clear trigger and sequencing. It stops short of naming the sibling to use for the initial search (news) or stating when not to call it, so it is not a full when/when-not/alternatives statement.

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

All NewsMCP 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.

Resources

Need Help?