Skip to main content
Glama

get_build_log

Retrieve and analyze Zuul CI build logs to identify errors, filter with regex patterns, and view specific line ranges for debugging.

Instructions

Read, search, and navigate build log files with grep, line ranges, and error summary.

Args: uuid: Build UUID tenant: Tenant name (uses default if empty) log_name: Log file to read (default "job-output.txt"). For other files, use the path relative to the build's log_url, e.g. "logs/controller/ci-framework-data/logs/ci_script_008_run.log" mode: "summary" (default: tail + error lines) or "full" (paginated chunks) lines: For summary: tail line count (default 100). For full: offset start line. start_line: Read from this line number (1-based). If set with end_line, returns exactly that range (overrides mode). end_line: Read up to this line number (1-based, inclusive). grep: Python regex pattern to filter log lines (overrides mode). Use | for OR: "error|failed|timeout". Do NOT use backslash-pipe. context: Lines of context before/after each grep match (default 0, max 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes
tenantNo
log_nameNojob-output.txt
modeNosummary
linesNo
start_lineNo
end_lineNo
grepNo
contextNo

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imatza-rh/mcp-zuul'

If you have feedback or need assistance with the MCP directory API, please join our Discord server