Dynamoi

Preview Smart Link Themes

dynamoi_preview_smart_link_themes

Read-only

Use this when the user asks what Dynamoi Smart Link pages can look like, wants to compare Smart Link themes, or asks to preview the available themes before creating or updating a free Smart Link. This is a read-only visual preview and does not create, publish, update, or promote a Smart Link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dynamoi_preview_smart_link_themes"
  }
}

Input Schema

Name	Required	Description	Default
`artistName`	No
`releaseTitle`	No

Output Schema

Name	Required	Description	Default
`code`	No
`data`	No
`kind`	No
`field`	No
`status`	Yes
`draftId`	No
`message`	No
`retryable`	No
`nextAction`	No
`failureStage`	No
`prerequisite`	No
`screeningResult`	No
`retryAfterSeconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / properties / code / enum

Previous value: -[
-  "ACCOUNT_READ_ONLY",
-  "INVALID_SPOTIFY_SOURCE",
-  "CAPABILITY_REQUIRED",
-  "INSUFFICIENT_SCOPE",
-  "STATE_CONFLICT",
-  "QUOTE_CHANGED",
-  "RATE_LIMITED",
-  "OUTPUT_INVALID",
-  "UNKNOWN_EFFECT"
-]New value: +[
+  "ACCOUNT_READ_ONLY",
+  "INVALID_SPOTIFY_SOURCE",
+  "CAPABILITY_REQUIRED",
+  "INSUFFICIENT_SCOPE",
+  "TENANT_ACCESS_DENIED",
+  "STATE_CONFLICT",
+  "QUOTE_CHANGED",
+  "RATE_LIMITED",
+  "OUTPUT_INVALID",
+  "UNKNOWN_EFFECT"
+]

Changed3 schema fields changedSep 24, 2026

addedOutput schema / properties / draftId

Added value: +{
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}

addedOutput schema / properties / failureStage

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / screeningResult

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

Changed2 schema fields changedSep 23, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed2 schema fields changedSep 20, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedOutput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

Changed6 schema fields changedSep 10, 2026

addedOutput schema / properties / code

Added value: +{
+  "enum": [
+    "ACCOUNT_READ_ONLY",
+    "INVALID_SPOTIFY_SOURCE",
+    "CAPABILITY_REQUIRED",
+    "INSUFFICIENT_SCOPE",
+    "STATE_CONFLICT",
+    "QUOTE_CHANGED",
+    "RATE_LIMITED",
+    "OUTPUT_INVALID",
+    "UNKNOWN_EFFECT"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / field

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / nextAction

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "field": {
+      "maxLength": 120,
+      "minLength": 1,
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "provide_input",
+        "read_status",
+        "reconnect",
+        "handoff"
+      ],
+      "type": "string"
+    },
+    "reason": {
+      "maxLength": 240,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / prerequisite

Added value: +{
+  "maxLength": 240,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / retryAfterSeconds

Added value: +{
+  "maximum": 86400,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / retryable
```
Added value: +{
+  "type": "boolean"
+}
```

Changed6 schema fields changedAug 29, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
addedOutput schema / properties / data / properties / artistName
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / releaseTitle
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / properties / themes

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "publicUrl": {
+        "type": "string"
+      },
+      "summary": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "artistName",
+  "releaseTitle",
+  "themes"
+]

removedOutput schema / properties / kind / enum

Removed value: -[
-  "validation",
-  "business",
-  "platform",
-  "unknown"
-]

Changed4 schema fields changedAug 7, 2026

changedOutput schema / additionalProperties
```
Previous value: -{}New value: +false
```

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": {},
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "enum": [
+    "validation",
+    "business",
+    "platform",
+    "unknown"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```

AddedJun 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by characterizing the output as a visual preview and enumerating the mutations it will not perform (create/publish/update/promote), which reassures an agent about side effects.

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?

Two tight sentences with the primary use case front-loaded and no filler. The second sentence is somewhat redundant with the readOnly/destructive annotations but still earns its place as an explicit no-side-effects statement.

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 zero-required-parameter, read-only preview tool with an output schema and full annotation coverage, the description covers purpose, triggers, and safety adequately. The only real gap is the meaning of the two input parameters, which nothing in the definition explains.

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?

Two parameters (artistName, releaseTitle) have 0% schema description coverage and no mention in the description at all. An agent cannot tell from either source whether these are sample values used to render the preview or whether they are required filters, and their optionality is only visible in the schema.

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 (preview) and resource (Smart Link themes) and immediately scopes it as a visual preview of what Smart Link pages look like. The closing negation (does not create, publish, update, or promote a Smart Link) cleanly separates it from sibling write tools like dynamoi_create_smart_link_from_spotify and dynamoi_update_smart_link.

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 trigger conditions: user asks what Smart Link pages can look like, wants to compare themes, or wants to preview before creating/updating. It does not, however, name the sibling tool an agent should pick instead for the actual creation/update path, so the routing is only implied by the negation.

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

All Dynamoi 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.