Dynamoi

List Campaigns

dynamoi_list_campaigns

Read-only

Use this when the user wants to browse campaigns for one artist, optionally filtered by type or status. Do not use this for a single campaign deep dive; use dynamoi_get_campaign for that. Never use this to personalize generic marketing advice. If the user has no artists yet, do not call this — route via dynamoi_get_account_overview first.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`format`	No
`status`	No
`artistId`	Yes
`campaignType`	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 8, 2026

changedInput schema / properties / status / enum

Previous value: -[
-  "AWAITING_SMART_LINK",
-  "ACTIVE",
-  "ARCHIVED",
-  "CONTENT_VALIDATION",
-  "DEPLOYING",
-  "FAILED",
-  "PAUSED",
-  "READY_FOR_REVIEW",
-  "SUBSCRIPTION_PAUSED"
-]New value: +[
+  "AWAITING_SMART_LINK",
+  "ACTIVE",
+  "ARCHIVED",
+  "CONTENT_VALIDATION",
+  "DEPLOYING",
+  "ENDED",
+  "FAILED",
+  "PAUSED",
+  "READY_FOR_REVIEW",
+  "SUBSCRIPTION_PAUSED"
+]

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

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 / properties / nextCursor
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / summary
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / totalCount
```
Added value: +{
+  "type": "number"
+}
```

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

Changed1 schema field changedMay 29, 2026

addedInput schema / properties / status / enum

Added value: +[
+  "AWAITING_SMART_LINK",
+  "ACTIVE",
+  "ARCHIVED",
+  "CONTENT_VALIDATION",
+  "DEPLOYING",
+  "FAILED",
+  "PAUSED",
+  "READY_FOR_REVIEW",
+  "SUBSCRIPTION_PAUSED"
+]

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds genuine non-schema context: the prerequisite that an artist must exist and the redirect path when it does not. It stops short of describing pagination behavior (limit/cursor) or the json vs summary format trade-off.

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 front-loaded, with the positive use case first, the sibling exclusion second, and the precondition last. No filler or restated name/title text; every sentence carries routing or constraint information an agent needs.

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 list tool with an output schema, return-value explanation is unnecessary, and the annotations cover safety. The description handles routing and disqualification well, but the operator-level details an agent would need (pagination, format selection) are absent from both description and schema.

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

Parameters3/5

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

Schema description coverage is 0% across six parameters, so the description must carry the load. It does cover the artist scoping and the two filter params (type, status), but says nothing about limit (max 50), cursor-based pagination, or the format enum (json/summary), leaving three of six parameters undocumented anywhere.

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 and resource (browse campaigns) scoped to one artist, plus the optional filter dimensions (type, status). It explicitly carves out the boundary against dynamoi_get_campaign, so an agent can distinguish the two without inspecting either schema.

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?

Provides explicit when-to-use, when-not-to-use ('Do not use this for a single campaign deep dive'), names the alternative tool, and adds a routing precondition ('If the user has no artists yet... route via dynamoi_get_account_overview first'). This is about as complete as usage guidance gets.

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.