Opsphere — DevOps & SRE Intelligence

GHE Actions: Jobs of Latest Run

ghe_actions_latest_jobs

Read-only

List jobs and steps of the latest run of a repo.

Input Schema

Name	Required	Description
`repo`	Yes	Repository name or full owner/name slug. Prefer owner/name when known so routing never depends on a workspace default.
`owner`	No	Optional GitHub org/user. A full repo slug (owner/name) takes precedence; otherwise the active workspace default org is used.
`branch`	No
`workflow`	No
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / issues

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / data / properties / jobs

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "completedAt": {
+        "$ref": "#/properties/data/properties/run/properties/createdAt"
+      },
+      "conclusion": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "startedAt": {
+        "$ref": "#/properties/data/properties/run/properties/createdAt"
+      },
+      "status": {
+        "type": "string"
+      },
+      "steps": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "conclusion": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name": {
+              "type": "string"
+            },
+            "number": {
+              "type": "integer"
+            },
+            "status": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "status",
+            "conclusion",
+            "number"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "status",
+      "conclusion"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / maxResults
```
Removed value: -{
-  "type": "number"
-}
```
removedOutput schema / properties / data / properties / nextPageToken
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / query

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "branch": {
+      "type": "string"
+    },
+    "owner": {
+      "type": "string"
+    },
+    "repo": {
+      "type": "string"
+    },
+    "workflow": {
+      "type": [
+        "string",
+        "number"
+      ]
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / data / properties / results

Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}

addedOutput schema / properties / data / properties / run

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "actor": {
+      "type": "string"
+    },
+    "branch": {
+      "type": "string"
+    },
+    "conclusion": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "createdAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "durationSeconds": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "htmlUrl": {
+      "type": "string"
+    },
+    "id": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "$ref": "#/properties/data/properties/run/properties/createdAt"
+    },
+    "workflowId": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "workflowId",
+    "status",
+    "conclusion",
+    "branch",
+    "createdAt",
+    "updatedAt",
+    "durationSeconds",
+    "htmlUrl"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / data / properties / startAt
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / status

Added value: +{
+  "enum": [
+    "ok",
+    "no_runs"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / data / properties / total
```
Removed value: -{
-  "type": "number"
-}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "status",
+  "query",
+  "partial",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description usefully clarifies that it returns both jobs and steps (not just job summaries), but it says nothing about behavior when the repo has no runs, whether runs are re-resolved on each call, or how filtering interacts with 'latest'.

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?

A single front-loaded sentence with no waste. It is terse, but the terseness is a symptom of missing content rather than padding, so it should not be penalized heavily here.

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

Completeness2/5

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

An output schema exists so return values need no explanation, but for a tool whose selection logic hinges on branch and workflow, the description leaves the agent unable to predict which run's jobs it will get or what happens on an empty result.

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

Parameters2/5

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

Schema coverage is 60%, and the two undocumented parameters, branch and workflow, are exactly the ones that determine which run is 'latest'. The description adds no meaning for them, leaving critical selection semantics undefined in both schema and prose.

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?

The description names a specific verb (List) and resource (jobs and steps) and scopes it to the latest run of a repo, which distinguishes it from ghe_actions_latest (run metadata) and ghe_actions_latest_logs (logs). It does not explicitly name those siblings, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to pick this over ghe_actions_latest, ghe_actions_latest_logs, or ghe_workflow_runs_list, nor any precondition such as 'a run must already exist'. The agent must guess from the name alone.

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

All Opsphere — DevOps & SRE Intelligence 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.

Resources

Need Help?