Skip to main content
Glama

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
formatNo
statusNo
artistIdYes
campaignTypeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNo
dataNo
kindNo
fieldNo
statusYes
draftIdNo
messageNo
retryableNo
nextActionNo
failureStageNo
prerequisiteNo
screeningResultNo
retryAfterSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
      +]
  2. Changed1 schema field changed
    • 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"
      +]
  3. Changed3 schema fields changed
    • 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"
      +}
  4. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  5. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  6. Changed6 schema fields changed
    • 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"
      +}
  7. Changed6 schema fields changed
    • 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"
      -]
  8. Changed4 schema fields changed
    • 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"
      +}
  9. Changed1 schema field changed
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "AWAITING_SMART_LINK",
      +  "ACTIVE",
      +  "ARCHIVED",
      +  "CONTENT_VALIDATION",
      +  "DEPLOYING",
      +  "FAILED",
      +  "PAUSED",
      +  "READY_FOR_REVIEW",
      +  "SUBSCRIPTION_PAUSED"
      +]
  10. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": {},
      +  "properties": {
      +    "status": {
      +      "enum": [
      +        "success",
      +        "partial_success",
      +        "error"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  11. First observed

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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.