agentView

Generate Display Preview Share Link

get_display_preview_url

Read-only

Creates a short-lived signed link showing what a display is presenting RIGHT NOW, rendered inline as a preview widget. ALWAYS call this when the user wants to SEE their display or screen content (preview, 'zeig mir das Display'). Link lifetime follows the display's privacy mode. Requires content scope.

Input Schema

TableJSON Schema

Name	Required	Description
`display_id`	Yes	The 8-character alphanumeric display profile ID, e.g. 'ABCD1234'.
`ttl_seconds`	No	Lifetime of the share link in seconds. Default 3600 (1 hour). Clamped to [60, 86400].
`access_token`	No	Optional bearer token; prefer session_request_id.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`displayId`	No
`expiresAt`	No
`previewUrl`	No
`ttlSeconds`	No
`displayName`	No
`privacyMode`	No
`contentVersionId`	No

Schema Changelog

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

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / session_request_id

Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}

Changed1 schema field changedJul 6, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication."New value: +"Optional bearer token; prefer session_request_id."

Changed8 schema fields changedJun 2, 2026

changedOutput schema / properties / contentVersionId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / displayId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / displayName / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / expiresAt / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / mode / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / previewUrl / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / privacyMode / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / ttlSeconds / type

Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]

Changed10 schema fields changedMay 23, 2026

removedInput schema / properties / access_token / default
```
Removed value: -null
```

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional JWT access token for authentication."

changedInput schema / properties / access_token / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

removedInput schema / properties / session_request_id

Removed value: -{
-  "default": null,
-  "description": "Optional session request ID returned by create_auth_session. Pass this instead of access_token for simpler, more reliable authentication when generating preview links for private displays.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedInput schema / properties / ttl_seconds / default
```
Removed value: -null
```

changedInput schema / properties / ttl_seconds / description

Previous value: -"Optional lifetime of the share link in seconds. Default 3600 (1 hour). Clamped to [60, 86400]."New value: +"Lifetime of the share link in seconds. Default 3600 (1 hour). Clamped to [60, 86400]."

addedInput schema / properties / ttl_seconds / maximum
```
Added value: +86400
```
addedInput schema / properties / ttl_seconds / minimum
```
Added value: +60
```

changedInput schema / properties / ttl_seconds / type

Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contentVersionId": {
+      "type": "string"
+    },
+    "displayId": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "expiresAt": {
+      "type": "string"
+    },
+    "mode": {
+      "type": "string"
+    },
+    "previewUrl": {
+      "type": "string"
+    },
+    "privacyMode": {
+      "type": "string"
+    },
+    "ttlSeconds": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedMay 8, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication."New value: +"Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically."

addedInput schema / properties / session_request_id

Added value: +{
+  "default": null,
+  "description": "Optional session request ID returned by create_auth_session. Pass this instead of access_token for simpler, more reliable authentication when generating preview links for private displays.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedMay 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already signal read-only and non-destructive behavior; the description adds meaningful context beyond that: short-lived signed link, inline preview rendering, lifetime coupling to privacy mode, and the content-scope requirement. No contradiction with readOnlyHint is present because creating a signed link does not imply mutating persistent state.

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?

Packs the key decision trigger, behavior, and a security requirement into four short sentences. The most actionable guidance ('ALWAYS call this when...') is front-loaded, with no redundant filler.

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 tool with one required parameter, full schema documentation, read-only annotations, and an output schema, the description supplies everything the agent needs to select and invoke it correctly: what it returns, when to use it, lifetime behavior, and required scope.

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 coverage is 100%, so the schema already documents every parameter thoroughly. The description adds contextual value like privacy-mode-based linking and content scope, but does not need to restate per-parameter semantics.

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?

Uses a specific verb and resource: 'Creates a short-lived signed link' showing current display content. The 'RIGHT NOW' and 'rendered inline as a preview widget' wording clearly differentiates it from broader display or read operations.

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?

Provides explicit trigger guidance: 'ALWAYS call this when the user wants to SEE their display or screen content (preview, zeig mir das Display).' It does not name specific alternative tools or state when not to use it, but the usage context is unambiguous.

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

All agentView 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

A4/5.0

Disambiguation4/5

Most tools map cleanly to distinct resource-action pairs (displays, organizations, assets, data slots, store templates, auth). A few clusters like the get_store_template_* family and the auth/session tools could still confuse an agent, but their descriptions are explicit enough to separate them.

Naming Consistency4/5

The dominant pattern is consistent verb_noun snake_case (list_*, get_*, create_*, delete_*, send_*, set_*, manage_*). Deviations like fetch, search, authenticate, logout, and pair_by_code are understandable but break the otherwise uniform naming scheme.

Tool Count1/5

With 57 tools this server far exceeds the 50+ threshold, creating an extreme tool-set size for an MCP server. Even though the underlying platform is feature-rich, the sheer number of tools heavily taxes context and selection.

Completeness4/5

The surface covers display, organization, asset, data slot, store template, auth, API key, and licensing lifecycles in impressive depth. Minor gaps exist, such as no delete operation for display categories and no reboot/power control for displays.

Resources

Need Help?