nowyourlink public Spotlights

list_spotlights

Read-onlyIdempotent

Browse settled public Spotlights, newest first, including labeled house advertisements. Removed ads are excluded.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`cursor`	No	Exclusive older-date cursor from nextCursor; cannot be combined with offset.
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 7, 2026

addedInput schema / not

Added value: +{
+  "required": [
+    "cursor",
+    "offset"
+  ]
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Exclusive older-date cursor from nextCursor; cannot be combined with offset.",
+  "format": "date",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "properties": {
-      "data": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "advertiser": {
-              "type": "string"
-            },
-            "canonicalUrl": {
-              "format": "uri",
-              "type": "string"
-            },
-            "contentType": {
-              "enum": [
-                "paid_advertisement",
-                "house_advertisement"
-              ],
-              "type": "string"
-            },
-            "day": {
-              "description": "Settled auction date in UTC, YYYY-MM-DD.",
-              "format": "date",
-              "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
-              "type": "string"
-            },
-            "description": {
-              "type": "string"
-            },
-            "headline": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "day",
-            "headline",
-            "description",
-            "advertiser",
-            "canonicalUrl",
-            "contentType"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "nextOffset": {
-        "type": [
-          "integer",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "data",
-      "nextOffset"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "detail": {
-        "type": "string"
-      },
-      "docs": {
-        "format": "uri",
-        "type": "string"
-      },
-      "status": {
-        "type": "integer"
-      },
-      "title": {
-        "type": "string"
-      },
-      "type": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "title",
-      "status",
-      "detail"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "data": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "advertiser": {
+              "type": "string"
+            },
+            "canonicalUrl": {
+              "format": "uri",
+              "type": "string"
+            },
+            "contentType": {
+              "enum": [
+                "paid_advertisement",
+                "house_advertisement"
+              ],
+              "type": "string"
+            },
+            "day": {
+              "description": "Settled auction date in UTC, YYYY-MM-DD.",
+              "format": "date",
+              "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+              "type": "string"
+            },
+            "description": {
+              "type": "string"
+            },
+            "headline": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "day",
+            "headline",
+            "description",
+            "advertiser",
+            "canonicalUrl",
+            "contentType"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "nextCursor": {
+        "anyOf": [
+          {
+            "description": "Settled auction date in UTC, YYYY-MM-DD.",
+            "format": "date",
+            "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "nextOffset": {
+        "type": [
+          "integer",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "data",
+      "nextOffset",
+      "nextCursor"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "detail": {
+        "type": "string"
+      },
+      "docs": {
+        "format": "uri",
+        "type": "string"
+      },
+      "status": {
+        "type": "integer"
+      },
+      "title": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "title",
+      "status",
+      "detail"
+    ],
+    "type": "object"
+  }
+]

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful result-set behavior beyond those annotations: newest-first ordering, inclusion of labeled house advertisements, and exclusion of removed ads. This goes beyond what annotations or schema convey.

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?

A single sentence with no filler; every clause adds information about scope, ordering, or filtering. It is front-loaded with the core action and resource.

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?

For a listing tool with an output schema and strong annotations, the description covers the content, ordering, and filters that matter most. It does not explain pagination beyond the cursor schema, but the schema and output schema fill that gap; the only notable omission is explicit guidance on when to use this vs the sibling get_* decriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: only cursor has a description. The description does not compensate by explaining limit, offset, or cursor pagination behavior; it only mentions sorting. An agent must infer the roles of limit and offset from their names and the cursor description.

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 uses a specific verb ('Browse') and a specific resource ('settled public Spotlights'), and adds sorting ('newest first') and inclusion/exclusion filters. Its plural collection scope clearly distinguishes it from the single-item sibling tools get_current_spotlight and get_spotlight.

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

Usage Guidelines3/5

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

The description implies this is the tool for browsing a filtered list of Spotlights, but it never explicitly says when to choose it over get_spotlight or get_current_spotlight. There are no stated alternatives or exclusion conditions, so usage guidance is left mostly to inference.

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

All nowyourlink public Spotlights 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.