Dynamoi

Get Smart Link

dynamoi_get_smart_link

Read-only

Use this when the user wants full details for one free Smart Link, including release, Spotify URL, public play.dynamoi.com URL, current status, theme source, and next actions. Set includeAnalytics=true for visit/click analytics and includeArtistSettings=true for artist-level theme/pixel settings. In the final answer, lead with the public URL and do not expose internal IDs unless asked.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No
`artistId`	No
`dateRange`	No
`playLinkId`	No
`spotifyUrl`	No
`granularity`	No
`includeAnalytics`	No
`includeBreakdowns`	No
`includeArtistSettings`	No

Output Schema

TableJSON 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.

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"
+}
```

Changed12 schema fields changedAug 29, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedOutput schema / properties / data / properties / artistId
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / artistName
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / id
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / name
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / nextActions
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / data / properties / publicUrl
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / publishState
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / releaseTitle
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / theme
```
Added value: +{
+  "type": "string"
+}
```
- 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"
+}
```

Changed3 schema fields changedMay 29, 2026

removedInput schema / properties / include

Removed value: -{
-  "items": {
-    "enum": [
-      "analytics",
-      "artist_settings"
-    ],
-    "type": "string"
-  },
-  "maxItems": 2,
-  "type": "array"
-}

addedInput schema / properties / includeAnalytics
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / includeArtistSettings
```
Added value: +{
+  "type": "boolean"
+}
```

Changed4 schema fields changedMay 5, 2026

addedInput schema / properties / dateRange

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "end": {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    "start": {
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "end",
+    "start"
+  ],
+  "type": "object"
+}

addedInput schema / properties / granularity

Added value: +{
+  "enum": [
+    "TOTAL",
+    "DAILY"
+  ],
+  "type": "string"
+}

addedInput schema / properties / include

Added value: +{
+  "items": {
+    "enum": [
+      "analytics",
+      "artist_settings"
+    ],
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}

addedInput schema / properties / includeBreakdowns
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedMay 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": {},
+  "properties": {
+    "status": {
+      "enum": [
+        "success",
+        "partial_success",
+        "error"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedMay 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it instructs the agent to lead with the public URL in the final answer and to avoid exposing internal IDs unless asked. It also clarifies that includeAnalytics and includeArtistSettings control optional data inclusion. It does not mention rate limits or pagination, but for a read-only single-resource tool this is adequate.

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?

Three sentences, all information-dense and front-loaded. The first sentence states the tool's purpose and output categories; the second explains the two optional flags; the third gives output presentation guidance. No filler or repetition of schema details.

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?

The tool has 9 parameters, 0 required, an output schema, and nested objects, so complexity is moderate. The description covers the tool's purpose, key optional flags, and output presentation. It does not explain several parameters (format, dateRange, granularity, includeBreakdowns, artistId) or how they interact, but the output schema and the tool's read-only nature reduce the risk of misuse. A 4 is appropriate; a 5 would require covering the remaining parameters or explicitly routing to siblings.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden for parameter meaning. It explicitly explains includeAnalytics and includeArtistSettings, which are otherwise bare booleans in the schema. It also names the resource being fetched (Smart Link) and the output categories, which helps infer playLinkId/spotifyUrl semantics. However, it does not explain format, dateRange, granularity, includeBreakdowns, or artistId, leaving several parameters under-documented.

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 states a specific verb ('get'), a specific resource ('one free Smart Link'), and enumerates the exact detail categories returned (release, Spotify URL, public URL, status, theme source, next actions). It also distinguishes itself from siblings by focusing on a single Smart Link's full details, which is distinct from list_smart_links and create_smart_link tools.

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?

The description opens with 'Use this when the user wants full details for one free Smart Link', which gives clear context for when to invoke it. It also explains when to set includeAnalytics and includeArtistSettings. However, it does not explicitly state when NOT to use it or name alternative tools like list_smart_links or get_artist_analytics, so it misses the exclusion/alternative guidance that would earn a 5.

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.