nowyourlink public Spotlights

List 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.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description goes further by disclosing ordering (newest first), inclusion of labeled house advertisements, and exclusion of removed ads – genuine behavioral traits beyond the structured fields.

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 tight sentence with zero filler, front-loading the resource and the two most decision-relevant facts (ordering and filtering). Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The remaining gap is pagination semantics for limit/offset, which neither the description nor the schema documents.

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%: cursor is documented in the schema, but limit and offset carry no description and the tool description adds no meaning for any of them. With a low coverage ratio, the description should compensate for pagination semantics but does not.

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?

States a specific verb ('Browse') and resource ('Spotlights') and adds scope: settled, public, newest first, house ads labeled, removed ads excluded. This clearly distinguishes it from the get_* siblings that return a single spotlight, though it never names them explicitly.

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 listing framing implies this is the tool for browsing multiple spotlights vs. get_spotlight/get_current_spotlight for single items, but there is no explicit when-to-use, when-not, or alternative naming. Usage is inferable but not stated.

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.