Ai Briefing

Get Timeline

get_timeline

Read-onlyIdempotent

Get a chronological timeline of AI developments between two dates. Returns events ordered by date with descriptions for understanding a specific period.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 50)
`category`	No	Optional category filter
`end_date`	No	End date YYYY-MM-DD (default: today)
`start_date`	Yes	Start date YYYY-MM-DD

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes	Number of events in timeline
`end_date`	Yes	Timeline end date
`timeline`	Yes	Chronological events
`start_date`	Yes	Timeline start date

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "end_date": "2025-01-15",
+    "start_date": "2025-01-01"
+  },
+  {
+    "category": "model_release",
+    "start_date": "2024-12-01"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "end_date": {
+      "description": "Timeline end date",
+      "type": "string"
+    },
+    "start_date": {
+      "description": "Timeline start date",
+      "type": "string"
+    },
+    "timeline": {
+      "description": "Chronological events",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Event category",
+            "type": "string"
+          },
+          "date": {
+            "description": "Event date in YYYY-MM-DD format",
+            "type": "string"
+          },
+          "importance": {
+            "description": "Importance level",
+            "type": "string"
+          },
+          "source": {
+            "description": "Source identifier",
+            "type": "string"
+          },
+          "summary": {
+            "description": "Event summary",
+            "type": "string"
+          },
+          "title": {
+            "description": "Event title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Source URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Number of events in timeline",
+      "type": "number"
+    }
+  },
+  "required": [
+    "start_date",
+    "end_date",
+    "total",
+    "timeline"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "limit": 25
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Number of statuses returned",
-      "type": "number"
-    },
-    "statuses": {
-      "description": "Recent public timeline posts",
-      "items": {
-        "properties": {
-          "account": {
-            "description": "Author account info",
-            "properties": {
-              "acct": {
-                "description": "Full account address",
-                "type": "string"
-              },
-              "display_name": {
-                "description": "Display name",
-                "type": "string"
-              },
-              "id": {
-                "description": "Account ID",
-                "type": "string"
-              },
-              "username": {
-                "description": "Username",
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          "content": {
-            "description": "Post content/body",
-            "type": "string"
-          },
-          "created_at": {
-            "description": "Post creation timestamp",
-            "type": "string"
-          },
-          "favourites_count": {
-            "description": "Number of favorites",
-            "type": "number"
-          },
-          "id": {
-            "description": "Status ID",
-            "type": "string"
-          },
-          "language": {
-            "description": "Post language code",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "reblogs_count": {
-            "description": "Number of reblogs/shares",
-            "type": "number"
-          },
-          "replies_count": {
-            "description": "Number of replies",
-            "type": "number"
-          },
-          "sensitive": {
-            "description": "Content warning flag",
-            "type": "boolean"
-          },
-          "spoiler_text": {
-            "description": "Content warning text",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "tags": {
-            "description": "Hashtags in post",
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          "url": {
-            "description": "Status URL",
-            "type": "string"
-          },
-          "visibility": {
-            "description": "Visibility level",
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "statuses"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of statuses returned",
+      "type": "number"
+    },
+    "statuses": {
+      "description": "Recent public timeline posts",
+      "items": {
+        "properties": {
+          "account": {
+            "description": "Author account info",
+            "properties": {
+              "acct": {
+                "description": "Full account address",
+                "type": "string"
+              },
+              "display_name": {
+                "description": "Display name",
+                "type": "string"
+              },
+              "id": {
+                "description": "Account ID",
+                "type": "string"
+              },
+              "username": {
+                "description": "Username",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "content": {
+            "description": "Post content/body",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "Post creation timestamp",
+            "type": "string"
+          },
+          "favourites_count": {
+            "description": "Number of favorites",
+            "type": "number"
+          },
+          "id": {
+            "description": "Status ID",
+            "type": "string"
+          },
+          "language": {
+            "description": "Post language code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reblogs_count": {
+            "description": "Number of reblogs/shares",
+            "type": "number"
+          },
+          "replies_count": {
+            "description": "Number of replies",
+            "type": "number"
+          },
+          "sensitive": {
+            "description": "Content warning flag",
+            "type": "boolean"
+          },
+          "spoiler_text": {
+            "description": "Content warning text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tags": {
+            "description": "Hashtags in post",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "description": "Status URL",
+            "type": "string"
+          },
+          "visibility": {
+            "description": "Visibility level",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "statuses"
+  ],
+  "type": "object"
+}

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

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that results are ordered by date and include descriptions, which is helpful but adds only moderate behavioral context beyond what annotations provide.

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 action and resource, followed by details on ordering and purpose. No wasteful words.

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 the tool has an output schema and the description covers the essential purpose and result characteristics (chronological order, descriptions), it is mostly complete. Minor omission: it doesn't specify the source or scope of 'AI developments', but that's implied by the tool context.

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 the baseline is 3. The description does not add any additional parameter semantics beyond what is already in the schema.

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 it retrieves a chronological timeline of AI developments between two dates, with events ordered by date and descriptions. This distinguishes it from siblings like get_ai_news or get_recent, though it doesn't explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives. It lacks instructions on when not to use it or which sibling tools might be more appropriate for other scenarios.

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

All Ai Briefing tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Many tools have overlapping purposes, such as multiple tools for querying Pipeworx data (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) and numerous tools for AI news/tools (get_ai_news, get_ai_toolbelt, get_briefing, get_model_landscape, etc.). This will cause an agent to frequently misselect the appropriate tool.

Naming Consistency4/5

Most tools follow a verb_noun pattern in snake_case (e.g., compare_entities, discover_tools, get_briefing). However, a few deviate like 'bet_research' (noun_verb) and 'what_happened' (phrase), but overall the pattern is largely consistent.

Tool Count2/5

38 tools is excessive for a server called 'Ai Briefing', which suggests a focused purpose. The tool count spans multiple domains (AI visibility, Pipeworx queries, Polymarket betting, memory, subscriptions) making it feel overstuffed and unfocused.

Completeness3/5

The tool set covers many aspects of its broad domain (querying, comparing, subscribing, memory), but there are notable gaps: no tool for modifying subscriptions, no user profile management, and the AI news tools overlap rather than cover distinct needs.

Get Timeline

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources