Opsphere — DevOps & SRE Intelligence

GHE Actions: Logs (preview) of Latest Run

ghe_actions_latest_logs

Read-only

Download the ZIP of logs from the latest run and return a concatenated preview.

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.
`previewBytes`	No	Preview size in bytes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 26, 2026

addedOutput schema / properties / data / properties / entries

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "level": {
+        "enum": [
+          "trace",
+          "debug",
+          "info",
+          "warn",
+          "error",
+          "fatal",
+          "unknown"
+        ],
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "timestamp": {
+        "$ref": "#/properties/data/properties/run/properties/createdAt"
+      },
+      "traceId": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / format

Removed value: -{
-  "enum": [
-    "plain",
-    "markdown",
-    "json"
-  ],
-  "type": "string"
-}

addedOutput schema / properties / data / properties / gaps

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

addedOutput schema / properties / data / properties / logExcerpt
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / previewBytes

Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}

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"
+}

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"
+}

addedOutput schema / properties / data / properties / signatures

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "count": {
+        "type": "integer"
+      },
+      "pattern": {
+        "type": "string"
+      },
+      "sampleMessage": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "pattern",
+      "count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / status

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

removedOutput schema / properties / data / properties / text
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

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

changedOutput schema / properties / data / required

Previous value: -[
-  "text"
-]New value: +[
+  "status",
+  "query",
+  "previewBytes",
+  "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

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real context beyond them: it fetches a ZIP artifact and returns a truncated concatenated preview, not the full archive. It omits auth/permission requirements and that truncation is governed by previewBytes.

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?

One sentence, front-loaded with the action and resource, with the output behavior attached. No filler or redundancy.

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

Completeness3/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 with 6 parameters and two undocumented in the schema, the description leaves the branch/workflow selection semantics and preview truncation ambiguous for a tool whose whole purpose is filtered latest-run retrieval.

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 67%; branch and workflow are undocumented in the schema, and the description does not explain that supplying branch/workflow narrows which run counts as 'latest'. It also adds nothing about previewBytes controlling the preview cutoff. Baseline 3 for partial schema coverage with marginal added meaning.

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 ('Download the ZIP of logs from the latest run') and even describes the return shape ('concatenated preview'). An agent can distinguish it from siblings like ghe_actions_latest (metadata) and ghe_actions_latest_jobs (job list), though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'latest run' — reach for this when you need raw log text rather than run/job metadata — but there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g. pointing at ghe_actions_diagnose for analysis).

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?