Skip to main content
Glama
AIops-tools

cicd-aiops

job_trace_tail

Fetch the tail of a job's trace to pinpoint the error. Returns the most recent log lines plus truncation flags, so you can raise tail_lines if the first failure may lie above the window.

Instructions

[READ] The tail of one job's log/trace — where the failure explains itself.

Returns {project, job, trace, totalLines, tailLines, returned, limit, truncated, charsTruncated}. 'truncated' true means earlier lines were dropped (the trace is only the tail — the FIRST error may be above the window, so raise tail_lines before concluding a root cause); 'charsTruncated' true means the tail itself hit the byte ceiling.

Args: project: Project id or full path. job: Job id (from pipeline_jobs). tail_lines: How many trailing lines to return (default 60). target: Server target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobYes
targetNo
projectYes
tail_linesNo
Behavior5/5

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

Discloses key behaviors: truncation of earlier lines and byte ceiling, and the meaning of return flags. Since no annotations are provided, the description fully covers transparency.

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?

Well-organized with a clear header, return value description, and bullet-style args. No unnecessary text; every sentence adds value.

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?

Completely describes the return object with all fields, explains truncation conditions, and covers all parameters. No output schema exists, so the description fulfills that need thoroughly.

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

Parameters5/5

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

Despite 0% schema coverage, the description contains an 'Args' section that explains all four parameters, including default values and sources for parameters like job id.

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?

The description clearly states it is a READ operation retrieving the tail of a job's log/trace, explicitly mentioning the return fields and distinguishing itself from sibling tools like pipeline_failure_rca by focusing on the raw trace tail.

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?

Provides guidance on when to increase tail_lines if truncated, and indicates how to obtain the job id. While it does not explicitly state when not to use, the context is sufficient for proper tool selection.

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

Install Server

Other Tools

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/AIops-tools/CICD-AIops'

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