raumnebenan

List stories

list_stories

Read-onlyIdempotent

Lists all published stories (thematic groups of articles) with their nested articles (slug, title, summary, category, dates, and URLs). Use it to explore the complete content hierarchy and thematic structure. Large response; use page/per to read it in slices, or get_stories_by_category when a category is already known. Optional page/per return a slice and next_page while more remain; without them the complete list is returned.

Input Schema

Name	Required	Description	Default
`per`	No	Optional items per page (default 20 when page is set, max 100).
`page`	No	Optional 1-based page. Omit both page and per to receive the complete list.

Output Schema

Name	Required	Description	Default
`data`	Yes
`source`	Yes
`retrieved_at`	Yes
`copyright_holder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

addedInput schema / properties / page

Added value: +{
+  "description": "Optional 1-based page. Omit both page and per to receive the complete list.",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per

Added value: +{
+  "description": "Optional items per page (default 20 when page is set, max 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / next_page

Added value: +{
+  "description": "The next page number; absent on the last page.",
+  "minimum": 2,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / page

Added value: +{
+  "description": "The returned page (1-based).",
+  "minimum": 1,
+  "type": "integer"
+}

addedOutput schema / properties / data / properties / per

Added value: +{
+  "description": "Items per page.",
+  "minimum": 1,
+  "type": "integer"
+}

Changed5 schema fields changedOct 16, 2026

addedOutput schema / properties / data

Added value: +{
+  "properties": {
+    "stories": {
+      "description": "The list of stories.",
+      "items": {
+        "properties": {
+          "articles": {
+            "description": "Articles in this story.",
+            "items": {
+              "properties": {
+                "article_slug": {
+                  "type": "string"
+                },
+                "article_uuid": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "category": {
+                  "type": "string"
+                },
+                "story_slug": {
+                  "type": "string"
+                },
+                "summary": {
+                  "type": "string"
+                },
+                "title": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "article_slug",
+                "article_uuid",
+                "title"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "category": {
+            "type": "string"
+          },
+          "last_story_update": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "original_publishing_date": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "source_url": {
+            "format": "uri",
+            "type": "string"
+          },
+          "story_slug": {
+            "type": "string"
+          },
+          "story_uuid": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "original_publishing_date",
+          "last_story_update",
+          "title",
+          "summary",
+          "story_slug",
+          "source_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "The total number of stories.",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total",
+    "stories"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / retrieved_at

Added value: +{
+  "format": "date-time",
+  "type": "string"
+}

removedOutput schema / properties / source_friendly_url
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / stories

Removed value: -{
-  "items": {
-    "properties": {
-      "articles": {
-        "items": {
-          "properties": {
-            "article_slug": {
-              "type": "string"
-            },
-            "article_uuid": {
-              "type": "string"
-            },
-            "last_article_update": {
-              "type": "string"
-            },
-            "original_publishing_date": {
-              "type": "string"
-            },
-            "summary": {
-              "type": "string"
-            },
-            "title": {
-              "type": "string"
-            }
-          },
-          "required": [],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "last_story_update": {
-        "type": "string"
-      },
-      "original_publishing_date": {
-        "type": "string"
-      },
-      "story_slug": {
-        "type": "string"
-      },
-      "story_uuid": {
-        "type": "string"
-      },
-      "summary": {
-        "type": "string"
-      },
-      "title": {
-        "type": "string"
-      }
-    },
-    "required": [],
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / required

Previous value: -[]New value: +[
+  "source",
+  "copyright_holder",
+  "retrieved_at",
+  "data"
+]

First observedJun 2, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds valuable behavioral context: responses are large, page/per yield slices with a next_page token while more remain, and omitting both returns the complete list. It does not quantify size or mention rate limits, but the pagination contract is clearly disclosed.

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 tightly packed sentences: purpose and contents first, then usage, then pagination mechanics. Every clause carries information (nested fields listed, sizing warning, alternative tool, token behavior) with no filler.

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?

With zero required parameters, an output schema present, and full schema coverage, the remaining agent questions are response size and pagination behavior, both of which are answered. Nothing needed to invoke 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 description coverage is 100%, so the baseline is 3, but the description adds semantics the schema lacks: the next_page token is returned while more results remain, and omitting both parameters changes behavior to 'complete list' rather than a default page.

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 (Lists) plus resource (published stories) and even disambiguates the domain term by defining stories as 'thematic groups of articles' with nested article fields. It is immediately distinguishable from siblings like list_articles and list_categories.

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?

Explicitly names the alternative route ('get_stories_by_category when a category is already known') and states the intended use ('explore the complete content hierarchy'). It also tells the agent when to paginate versus request everything.

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

All raumnebenan 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?