spinnaker-mcp

Overview Schema Source Related Servers Discussions Admin

List executions

list_executions

Read-onlyIdempotent

List recent Spinnaker pipeline executions for an application, optionally filtered by status, to monitor deployment activity or find an execution ID.

Instructions

List recent pipeline executions for a Spinnaker application, optionally filtered by status. Use this to monitor deployment activity or find a specific execution ID. Returns JSON array of execution summaries with status, timing, and trigger info. Use get_execution for full details of a specific run.

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": {
      "application": "<application>"
    },
    "name": "list_executions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of executions to return (default 25)
`statuses`	No	Comma-separated execution statuses to filter by (e.g. RUNNING,SUCCEEDED,TERMINAL,CANCELED)
`application`	Yes	Application name as registered in Spinnaker

Output Schema

Name	Required	Description	Default
`count`	No	Number of records in items.
`items`	No	The records, when Gate answered with a list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.4.1Nov 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of executions to return (default: 25)"New value: +"Maximum number of executions to return (default 25)"

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The Gate response. A JSON object from Gate comes back as is; a JSON array comes back as {items, count}.",
+  "properties": {
+    "count": {
+      "description": "Number of records in items.",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records, when Gate answered with a list.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0Apr 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds useful return context ('JSON array of execution summaries with status, timing, and trigger info') and the optional-status-filter behavior, though pagination and result ordering are not mentioned.

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 tight sentences with zero waste: purpose and filter first, use cases next, return shape and sibling hand-off last. Nothing is buried or repeated.

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?

With an output schema present, annotations covering safety, and full schema parameter coverage, the definition is nearly complete for a read-only list tool. The remaining gap is disambiguation from search_executions, which an agent could easily confuse when hunting a specific execution.

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 100%, with limit, statuses, and application all documented in the schema, so the baseline is 3. The description only restates that results can be filtered by status and are 'recent' (implying the limit), adding no syntax or semantic detail beyond the schema.

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 with scope: 'List recent pipeline executions for a Spinnaker application, optionally filtered by status.' It distinguishes itself from get_execution explicitly, but does not clarify how it differs from the sibling search_executions, which appears to overlap on 'find a specific execution ID'.

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 clear use cases ('monitor deployment activity or find a specific execution ID') and names an explicit alternative: 'Use get_execution for full details of a specific run.' It fails to address search_executions, the sibling with the most overlapping intent, so the routing guidance is incomplete rather than exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.