spinnaker-mcp

Overview Schema Source Related Servers Discussions Admin

Search executions

search_executions

Read-onlyIdempotent

Find pipeline executions by application, pipeline name, trigger type, status, or trigger time to locate runs matching specific criteria, such as failed webhook runs since yesterday.

Instructions

Search pipeline executions of an application by pipeline name, trigger type, status and trigger time. Use this instead of list_executions when you need executions matching specific criteria, for example every failed webhook run since yesterday. Returns a JSON array of executions, newest first, size per page (default 10).

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": "search_executions"
  }
}

Input Schema

Name	Required	Description
`size`	No	Executions per page (default 10)
`end_time`	No	Only executions triggered at or before this time, same formats as start_time
`event_id`	No	Only executions started by this trigger event ID
`statuses`	No	Comma-separated execution statuses (e.g. RUNNING,SUCCEEDED,TERMINAL,CANCELED,NOT_STARTED)
`start_time`	No	Only executions triggered at or after this time: RFC 3339 (2026-07-28T09:00:00Z), a date (2026-07-28, UTC midnight) or epoch milliseconds
`application`	Yes	Application name as registered in Spinnaker
`start_index`	No	Zero-based index of the first execution to return, for paging (default 0)
`trigger_type`	No	Trigger types, comma-separated (e.g. manual, webhook, cron, docker, jenkins, pipeline)
`pipeline_name`	No	Only executions of this pipeline (exact, case-sensitive name as shown in the UI)

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.

Changed9 schema fields changedv0.4.1Nov 1, 2026

changedInput schema / properties / end_time / description

Previous value: -"Filter executions started before this time (ISO 8601)"New value: +"Only executions triggered at or before this time, same formats as start_time"

changedInput schema / properties / event_id / description

Previous value: -"Filter by event ID"New value: +"Only executions started by this trigger event ID"

addedInput schema / properties / pipeline_name

Added value: +{
+  "description": "Only executions of this pipeline (exact, case-sensitive name as shown in the UI)",
+  "type": "string"
+}

addedInput schema / properties / size

Added value: +{
+  "description": "Executions per page (default 10)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / start_index

Added value: +{
+  "description": "Zero-based index of the first execution to return, for paging (default 0)",
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / start_time / description

Previous value: -"Filter executions started after this time (ISO 8601)"New value: +"Only executions triggered at or after this time: RFC 3339 (2026-07-28T09:00:00Z), a date (2026-07-28, UTC midnight) or epoch milliseconds"

changedInput schema / properties / statuses / description

Previous value: -"Comma-separated execution statuses to filter by (e.g. RUNNING,SUCCEEDED,TERMINAL)"New value: +"Comma-separated execution statuses (e.g. RUNNING,SUCCEEDED,TERMINAL,CANCELED,NOT_STARTED)"

changedInput schema / properties / trigger_type / description

Previous value: -"Filter by trigger type (e.g. manual, webhook, cron)"New value: +"Trigger types, comma-separated (e.g. manual, webhook, cron, docker, jenkins, pipeline)"

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.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered by structured data. The description adds real context beyond that: results are returned newest-first, as a JSON array, paged with a default size of 10. It stops short of anything else notable (e.g. total-count or whether filters are ANDed), so it is solid but not rich.

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, front-loaded with purpose, then the sibling routing rule, then return/paging behavior. Nothing is repeated and nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter read-only search with a fully described schema and an output schema present, the description covers what remains: purpose, sibling routing, ordering and paging default. An agent has everything needed to call it correctly.

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 100%, so every parameter is already documented with formats and examples, making 3 the baseline. The description only implicitly illustrates composition via the 'failed webhook run since yesterday' example, which hints at combining statuses, trigger_type and start_time but adds no syntax beyond the schema.

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 (search) and resource (pipeline executions) scoped to an application, and lists the filterable facets. It explicitly distinguishes itself from the sibling list_executions, so an agent can choose between them without opening 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?

Explicitly says to use this instead of list_executions when executions must match specific criteria, and gives a concrete scenario ('every failed webhook run since yesterday'). The alternative and the selecting condition are both named rather than left to inference.

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