Skip to main content
Glama

Retry workflow entries

campaignstack_retry_workflow_entries

Retry one or many failed workflow entries by explicit entry ids, or retry all failed entries at one node. Use selector type retry_waits after deploying a failure fix to wake auto_retry or condition_retry waits at one node, optionally matching errorMessageContains. Dispatch safety gates still apply. Follow the returned cursor until remaining is 0; remaining is a continuation indicator, not a total. Returns per-entry partial results for explicit ids and node batch counts for node selectors.

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": {
      "selector": "<selector>"
    },
    "name": "campaignstack_retry_workflow_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYes
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / selector / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "entryIds": {
      -        "items": {
      -          "minLength": 1,
      -          "type": "string"
      -        },
      -        "maxItems": 100,
      -        "minItems": 1,
      -        "type": "array"
      -      },
      -      "type": {
      -        "const": "entries",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "entryIds"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "nodeId": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "type": {
      -        "const": "node",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "type",
      -      "nodeId"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "entryIds": {
      +        "items": {
      +          "minLength": 1,
      +          "type": "string"
      +        },
      +        "maxItems": 100,
      +        "minItems": 1,
      +        "type": "array"
      +      },
      +      "type": {
      +        "const": "entries",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "entryIds"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "nodeId": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": {
      +        "const": "node",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "nodeId"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "cursor": {
      +        "type": "string"
      +      },
      +      "errorMessageContains": {
      +        "type": "string"
      +      },
      +      "nodeId": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "type": {
      +        "const": "retry_waits",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "type",
      +      "nodeId"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-readOnly, non-idempotent, non-destructive, closed-world mutation, so the safety profile is partly covered. The description adds meaningful behavior beyond that: dispatch safety gates still apply, pagination must be followed via cursor until remaining is 0, and remaining is explicitly a continuation indicator rather than a total. It leaves 'dispatch safety gates' undefined and says nothing about failure handling for individual entries.

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 sentences, front-loaded with the core retry action and selector modes, then the operational notes. Nearly every sentence earns its place, though 'Dispatch safety gates still apply' is terse to the point of being cryptic without further explanation.

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 two-parameter mutation with an output schema, the description covers selector choice, pagination continuation, and partial-result semantics for both selector types. The remaining gap is the unspecified nature of the dispatch safety gates, which could matter for an agent deciding whether a retry will actually take effect.

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 coverage is 50% and the workspaceId parameter already carries a thorough schema description, while the selector union is structurally self-documenting through its const types. The description adds real meaning for the retry_waits selector and errorMessageContains matching, but does not explain entryIds limits or cursor semantics beyond 'follow until remaining is 0', so it roughly matches rather than exceeds the schema's explanatory power.

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?

The description names a specific verb (retry) and resource (failed workflow entries) and states the two supported scoping modes: explicit entry ids or all failed entries at one node. An agent can distinguish this from siblings like campaignstack_cancel_workflow_node_leads or campaignstack_trigger_workflow without opening the schema.

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?

It gives a concrete when-to-use rule for the retry_waits selector (after deploying a failure fix, to wake auto_retry or condition_retry waits) and explains the entries-vs-node split. It stops short of stating when not to use the tool or naming a specific sibling alternative, so it is clear context rather than full routing guidance.

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.

Resources