Skip to main content
Glama

GitHub get job logs

github_get_job_logs
Read-only

Download and read the log output for a specific GitHub Actions job. Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Returns the actual console output from the job execution, showing build errors, test failures, and other details. Use this after getting workflow run jobs to read the logs for a failed job.

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": {
      "repo": "<repo>",
      "job_id": "<job_id>"
    },
    "name": "github_get_job_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name. Also accepts the combined 'owner/name' form.
ownerNoRepository owner (e.g. 'octocat'). Prefer the exact owner from a prior github_list_repositories call. May be omitted when the repository name is unambiguous in this organisation, or embedded in 'repo' as 'owner/name'.
job_idYesThe job ID. Get this from github_get_workflow_run_jobs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the important behavioral fact that the response is the raw console output of the job execution containing build errors and test failures. Gaps remain around log size/truncation and whether logs are fetched via redirect, which matter for an agent handling large outputs, but the return-content disclosure is substantive beyond the annotations.

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?

Front-loaded with the action and resource, then the prerequisite chain. Slight redundancy between 'Download and read the log output' and 'Returns the actual console output,' but every sentence contributes guidance the agent needs.

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 3-parameter read tool with full schema coverage and no output schema, the description covers what the call returns and how to obtain the inputs. Only ambiguous edge behavior (very large or truncated logs) is unaddressed.

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 the 'owner/name' combined form, the owner preference, and the job_id source are already documented in the schema. The description largely restates those points. Baseline 3 applies since the schema carries the parameter burden.

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?

Specific verb+resource ('Download and read the log output for a specific GitHub Actions job') with the scope narrowed to a single job. It is clearly distinguished from sibling tools like github_get_workflow_run_jobs, github_download_artifact, and get_pipeline_step_logs.

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?

Explicit sequencing: 'Use this after getting workflow run jobs to read the logs for a failed job,' which names the prerequisite tool and the failure-diagnosis scenario. It also tells the agent to prefer the exact owner from github_list_repositories. It lacks an explicit when-not-to-use (e.g. artifacts vs. logs), but the positive guidance is strong.

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.