Dynamoi

Update Smart Link

dynamoi_update_smart_link

DestructiveIdempotent

Use this when the user wants to change one Smart Link's public description or update artist-level Smart Link theme/pixel settings. Set action to update_description or update_artist_settings. Public availability is artist-wide in the dashboard; this tool does not publish or unpublish individual links. Theme-only updates switch instantly; description or pixel changes may queue background rendering.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`theme`	No
`action`	Yes
`artistId`	No
`playLinkId`	No
`metaPixelId`	No
`tiktokPixelId`	No
`clientRequestId`	No
`customDescription`	No
`expectedUpdatedAt`	No
`userIntentSummary`	No
`googleAdsConversionId`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`kind`	No
`status`	Yes
`message`	No

Schema Changelog

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

Changed11 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 / defaultTheme
```
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 / publicUrl
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / data / properties / renderQueuedCount
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / data / properties / renderWarning
```
Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
```
- addedOutput schema / properties / data / properties / summary
```
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"
+}
```

Changed2 schema fields changedJun 2, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "update_description",
-  "update_artist_settings",
-  "publish",
-  "unpublish"
-]New value: +[
+  "update_description",
+  "update_artist_settings"
+]

removedInput schema / properties / expectedPublishState

Removed value: -{
-  "enum": [
-    "published",
-    "unpublished"
-  ],
-  "type": "string"
-}

Changed8 schema fields changedMay 5, 2026

addedInput schema / properties / action

Added value: +{
+  "enum": [
+    "update_description",
+    "update_artist_settings",
+    "publish",
+    "unpublish"
+  ],
+  "type": "string"
+}

addedInput schema / properties / artistId

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

addedInput schema / properties / expectedPublishState

Added value: +{
+  "enum": [
+    "published",
+    "unpublished"
+  ],
+  "type": "string"
+}

addedInput schema / properties / googleAdsConversionId

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / metaPixelId

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedInput schema / properties / theme

Added value: +{
+  "enum": [
+    "classic",
+    "brutalist",
+    "aurora",
+    "cinematic"
+  ],
+  "type": "string"
+}

addedInput schema / properties / tiktokPixelId

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedInput schema / required

Previous value: -[
-  "customDescription",
-  "playLinkId"
-]New value: +[
+  "action"
+]

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

A3.9/5.0

Behavior4/5

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

Adds real behavioral context beyond annotations: two action modes, artist-wide scoping, no publish/unpublish, and sync vs background rendering. It does not detail destructive consequences despite destructiveHint=true, but annotations already flag that risk.

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?

Tight three sentences: trigger, action values, publishing boundary, and timing behavior. Every sentence earns its place with no repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, two-mode mutation tool with 0% schema coverage, this description is too thin. An agent cannot reliably know which IDs are required per action or what evidence fields like clientRequestId, expectedUpdatedAt, and userIntentSummary mean, even though an output schema exists.

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 0%, so the description carries the burden. It explains action's enum and the theme/pixel/description concepts, but leaves artistId, playLinkId, pixel IDs, clientRequestId, expectedUpdatedAt, userIntentSummary, and googleAdsConversionId unexplained and does not map parameters per action.

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 explicit use cases: changing a Smart Link's public description or updating artist-level theme/pixel settings. The update role is unambiguous against sibling create/get/list tools, and it explicitly rules out publish/unpublish behavior.

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?

Opens with 'Use this when...' and gives concrete triggers. It excluds publish/unpublish operations and clarifies artist-wide availability, though it does not name exact alternative tools for those cases.

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

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

A3.9/5.0

Disambiguation4/5

Most tools are cleanly separated by resource and action, and close pairs like account overview vs platform status and singular vs catalog smart-link creation are explicitly disambiguated. The main ambiguity is dynamoi_search versus the connector search tool, which both search the same entities and are distinguished only by chat vs deep-research context.

Naming Consistency4/5

The set overwhelmingly follows a consistent dynamoi_<verb>_<object> snake_case pattern, with predictable get/list/create/update verbs. The unprefixed fetch and search connector tools are a visible but small deviation from that convention.

Tool Count3/5

Seventeen tools is slightly heavy for the server's scope, especially since search/fetch partly duplicate dynamoi_search and the campaign domain is primarily read-only. The smart-link, artist, and distribution clusters each justify their tools, so it is not excessively bloated.

Completeness3/5

Smart links have create/list/get/update coverage and distribution has apply/status, but campaigns are only readable with no create/update/launch tool, despite get_campaign referencing campaign mutations. Platform connections also have status checks but no connect actions, leaving notable workflow gaps.

Update Smart Link

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources