Dynamoi

Update Smart Link Artist Settings

dynamoi_update_smart_link_artist_settings

DestructiveIdempotent

Use this when the user wants to change artist-level Smart Link theme or validated pixel settings. This tool only changes artist settings; it cannot change a link description or publish or unpublish links. Confirm the requested settings before calling. Theme-only changes switch instantly; pixel changes may queue background rendering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artistId": "<artistId>"
    },
    "name": "dynamoi_update_smart_link_artist_settings"
  }
}

Input Schema

Name	Required	Description	Default
`theme`	No
`artistId`	Yes
`metaPixelId`	No
`tiktokPixelId`	No
`clientRequestId`	No
`userIntentSummary`	No
`googleAdsConversionId`	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.

AddedOct 8, 2026
RemovedMay 5, 2026

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/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent, openWorld, and non-readOnly, so the bar is lower. The description adds genuinely useful behavioral context: theme-only changes apply instantly while pixel changes may queue background rendering, plus a confirmation safeguard. It doesn't warn that pixel IDs may overwrite existing values, a minor gap against destructiveHint=true.

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?

Front-loaded with the usage trigger, then scope exclusions and behavioral notes. Sentences are distinct and mostly earn their place, though the confirmation line is somewhat boilerplate.

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 values needn't be explained, and annotations carry the safety profile. The description covers scope, timing, and confirmation well; the main shortfall is under-explaining the several non-obvious request parameters.

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% across 7 parameters, so the description must carry the semantics. It loosely maps to theme and pixel settings but explains none of artistId, clientRequestId, userIntentSummary, or the enum values, leaving most parameters undocumented.

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+resource: 'change artist-level Smart Link theme or validated pixel settings.' It also bounds the resource precisely, excluding link description changes and publish/unpublish, which cleanly separates it from the sibling dynamoi_update_smart_link_description.

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 a clear when-to-use trigger ('Use this when the user wants to change...') and explicit exclusions ('cannot change a link description or publish or unpublish links'). It stops short of naming the alternative tools to call instead, but the scope boundary is effectively conveyed.

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.