Lobsters

Get Newest

get_newest

Read-onlyIdempotent

Get latest stories posted to Lobsters. Returns title, URL, publication time, score, and tags for each story.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`count`	No	Number of stories returned
`stories`	No	List of newest stories

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJun 2, 2026

changedOutput schema / properties / stories / items / properties / description / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```

removedOutput schema / properties / stories / items / properties / downvotes

Removed value: -{
-  "description": "Number of downvotes",
-  "type": "number"
-}

removedOutput schema / properties / stories / items / properties / submitter

Removed value: -{
-  "description": "Username of story submitter",
-  "type": "string"
-}

removedOutput schema / properties / stories / items / properties / upvotes

Removed value: -{
-  "description": "Number of upvotes",
-  "type": "number"
-}

removedOutput schema / properties / stories / items / required

Removed value: -[
-  "short_id",
-  "url",
-  "comments_url",
-  "title",
-  "score",
-  "upvotes",
-  "downvotes",
-  "comment_count",
-  "created_at",
-  "submitter",
-  "tags",
-  "description"
-]

removedOutput schema / required

Removed value: -[
-  "count",
-  "stories"
-]

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stories returned",
+      "type": "number"
+    },
+    "stories": {
+      "description": "List of newest stories",
+      "items": {
+        "properties": {
+          "comment_count": {
+            "description": "Number of comments",
+            "type": "number"
+          },
+          "comments_url": {
+            "description": "URL to view comments on Lobsters",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO timestamp of story creation",
+            "type": "string"
+          },
+          "description": {
+            "description": "Plain text description or null",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "downvotes": {
+            "description": "Number of downvotes",
+            "type": "number"
+          },
+          "score": {
+            "description": "Total score (upvotes - downvotes)",
+            "type": "number"
+          },
+          "short_id": {
+            "description": "Unique short ID for the story",
+            "type": "string"
+          },
+          "submitter": {
+            "description": "Username of story submitter",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Tags associated with the story",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Story title",
+            "type": "string"
+          },
+          "upvotes": {
+            "description": "Number of upvotes",
+            "type": "number"
+          },
+          "url": {
+            "description": "Story URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "short_id",
+          "url",
+          "comments_url",
+          "title",
+          "score",
+          "upvotes",
+          "downvotes",
+          "comment_count",
+          "created_at",
+          "submitter",
+          "tags",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stories"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds minimal behavioral context. It confirms the tool returns specific fields but does not disclose potential rate limits or other traits beyond what annotations indicate.

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?

The description is two concise sentences, front-loaded with the core purpose, and contains no extraneous information. Every sentence adds value.

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?

For a simple parameterless tool with an output schema, the description is complete. It specifies the source and return fields, which is sufficient for an agent to understand usage.

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?

There are no parameters, and schema description coverage is 100%, so the description does not need to add parameter details. It adds no extra meaning beyond the schema, which is adequate for a parameterless tool.

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 clearly states the tool retrieves the latest stories from Lobsters and specifies the return fields (title, URL, publication time, score, tags). It is specific and distinct from siblings like get_story, though it does not explicitly contrast with get_hottest.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as get_hottest or other story-related tools. No usage context or exclusions are given.

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

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