nightmarquee

by ant-dev-lab

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get a NightMarquee prompt

nightmarquee_get_prompt

Read-onlyIdempotent

Instructions

Fetch the full build prompt for one NightMarquee design, tuned for the target tool. When the account may download the demo's footage, the result also lists a short-lived link per clip: save each into public/ under its name before building. Free prompts need no account and their footage needs a free one; Unlimited prompts need Unlimited (run nightmarquee_sign_in).

Input Schema

Name	Required	Description
`slug`	Yes	Prompt slug, e.g. "glasshouse-nine" — from nightmarquee_search_prompts
`tool`	No	Target tool dialect. Defaults to codex when the client is Codex, otherwise claude
`brand`	No	Swap the fictional brand for this name

Output Schema

Name	Required	Description
`slug`	Yes
`text`	No	The full build prompt, present only when entitled
`tier`	No
`tool`	No	Dialect the text was written for
`error`	No	Set when the prompt could not be fetched
`title`	No
`demoUrl`	No
`footage`	No	The demo's footage, present when the account may download it
`entitled`	Yes	Whether the full build text is included; false means locked or missing
`pricingUrl`	No	Set when the prompt is locked
`footageMessage`	No	Why a demo with footage came without links, such as needing to sign in
`footageExpiresInSeconds`	No	How long the footage links work

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.6Oct 15, 2026

changedInput schema / properties / tool / description

Previous value: -"Target tool dialect, defaults to claude"New value: +"Target tool dialect. Defaults to codex when the client is Codex, otherwise claude"

changedInput schema / properties / tool / enum

Previous value: -[
-  "lovable",
-  "bolt",
-  "cursor",
-  "claude"
-]New value: +[
+  "lovable",
+  "bolt",
+  "cursor",
+  "claude",
+  "codex"
+]

addedOutput schema / properties / footage

Added value: +{
+  "description": "The demo's footage, present when the account may download it",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bytes": {
+        "type": "number"
+      },
+      "name": {
+        "description": "Save the file under this name, in public/",
+        "type": "string"
+      },
+      "role": {
+        "description": "What the clip shows and how the demo uses it",
+        "type": "string"
+      },
+      "seconds": {
+        "type": "number"
+      },
+      "url": {
+        "description": "Signed download link, valid for footageExpiresInSeconds",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "role",
+      "seconds",
+      "bytes",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / footageExpiresInSeconds

Added value: +{
+  "description": "How long the footage links work",
+  "type": "number"
+}

addedOutput schema / properties / footageMessage

Added value: +{
+  "description": "Why a demo with footage came without links, such as needing to sign in",
+  "type": "string"
+}

First observedv0.1.4Sep 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description goes further by disclosing that short-lived per-clip links may be returned and that each must be saved into public/ under its name before building. It also discloses the account/entitlement requirement per prompt tier, which is genuinely useful auth context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with the core action front-loaded in the first clause, and no filler. The footage/account sentence is long and packs three ideas together, slightly reducing scannability.

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 shape needn't be described, and the description still usefully flags the conditional footage links and the pre-build save step. Entitlement rules for each prompt tier are covered; what remains thin is guidance on how the target-tool dialect choice affects output.

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%, including the slug example, the tool enum default logic, and the brand swap note, so the schema carries the parameter burden. The description adds no further parameter-level detail (e.g., brand length limit, slug format), so the baseline 3 applies.

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 and resource ('Fetch the full build prompt for one NightMarquee design') plus the tuning dimension ('tuned for the target tool'). This distinguishes it from nightmarquee_search_prompts (discovery) and nightmarquee_get_footage (asset download) without needing to open schemas.

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

Usage Guidelines4/5

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

Gives explicit conditional guidance: footage links appear only when the account may download the demo's footage, free prompts need no account, Unlimited prompts need Unlimited and route to nightmarquee_sign_in. Lacks an explicit when-not-to-use or a direct contrast against nightmarquee_search_prompts/get_footage, so not a full 5.

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

Deploy Server