Dynamoi

Start YouTube Channel Link

dynamoi_start_youtube_channel_link

DestructiveIdempotent

Use this when the user wants to grow a YouTube channel with Dynamoi campaigns or is ready to link a channel to one Dynamoi artist from chat. Set purpose=distribution_identity for the least-privilege identity connection required by a distribution application; that flow does not require advertising billing or Google Ads linking, and its result is checked with dynamoi_get_distribution_application. Use purpose=advertising (the default) for managed YouTube promotion, then poll dynamoi_get_platform_status until platforms.youtube.connected is true. The tool returns a Google OAuth URL bound to the signed-in user and artist.

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

Input Schema

Name	Required	Description	Default
`format`	No
`purpose`	No
`artistId`	Yes
`userIntentSummary`	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.

AddedNov 2, 2026
RemovedAug 29, 2026

Changed1 schema field changedAug 25, 2026

addedInput schema / properties / purpose

Added value: +{
+  "enum": [
+    "advertising",
+    "distribution_identity"
+  ],
+  "type": "string"
+}

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

AddedMay 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond annotations, the description discloses that the tool returns an OAuth URL scoped to the signed-in user and artist, that distribution_identity is least-privilege and needs no advertising billing or Google Ads linking, and that polling is required. It does not explain the destructiveHint=true implication or the idempotent behavior, which are relevant for a mutation tool, but the operational context added is substantial.

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?

Four dense sentences that are front-loaded with the trigger and then the two purpose branches. Slight density in the middle sentences but no filler; each sentence conveys selection or follow-up guidance.

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?

Given a mutation tool with annotations and an output schema, the description covers triggering, purpose selection, follow-up polling, and return semantics (OAuth URL), which is what an agent needs to call correctly. Minor gaps are the format/userIntentSummary parameters and the destructive/idempotent implications.

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 burden. It thoroughly explains the ambiguous purpose enum (distribution_identity for least-privilege identity, advertising as default for managed promotion). It does not describe format or userIntentSummary, leaving two parameters uninterpreted, which keeps it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: grows a YouTube channel and links it to a Dynamoi artist. The final sentence clarifies that the tool returns a Google OAuth URL bound to the signed-in user and artist, which distinguishes it from the sibling dynamoi_start_meta_connection and the read-only status tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the two when-to-use branches (distribution_identity vs advertising), states which is default, and tells the agent what to do next in each case (check dynamoi_get_distribution_application vs poll dynamoi_get_platform_status until platforms.youtube.connected is true). This is a model routing instruction with defined alternatives.

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.