Skip to main content
Glama

Job output

job_output
Read-onlyIdempotent

Retrieve output from a background job or a truncated run_command that returned a job_id. Page through long build logs with offsetBytes and maxBytes so no output is lost.

Instructions

Fetch output of a background job, or of a finished run_command whose result was truncated (it reports a job_id). Supports paging through large output with offsetBytes/maxBytes, so nothing is lost even for very long build logs.

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": {
      "jobId": "<jobId>"
    },
    "name": "job_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoShort human-readable explanation (1 line, in the user's language) of what you are about to do and why. Shown to the user on the approval card. Always provide when calling mutating tools.
agentNoShort consistent identifier or display name of this agent (e.g. 'Claude · Лендинг', 'Тесты', 'Мой агент'). Used to separate tasks and route tray messages when multiple agents work in parallel.
jobIdYes
streamNo
maxBytesNo
offsetBytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds genuinely new context: paged retrieval via offsetBytes/maxBytes and the guarantee that long build logs are not lost. It stops short of describing default page sizing or the returned shape, but adds real value over annotations.

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?

A single tight sentence that front-loads the primary purpose, then the secondary use case, then the paging mechanism. No filler or redundant restatement of the title.

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 read-only fetch tool with no output schema, the description covers purpose, trigger conditions, and paging adequately. The note/agent parameters are documented in-schema, so their absence from the description is acceptable; only stream semantics remain a minor gap.

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?

At 33% schema coverage, the description compensates by explaining the paging pair (offsetBytes/maxBytes) and the origin of jobId. It does not explain the stream enum values or how 'both' interleaves stdout/stderr, leaving half the meaningful parameters undocumented in both places.

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?

States a specific verb and resource ('Fetch output of a background job') and additionally clarifies it serves truncated run_command results. This distinguishes it cleanly from job_status and run_command without needing schemas.

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?

Gives clear triggering conditions: after a background job, or when run_command reports a job_id due to truncation. It lacks an explicit 'use job_status to poll first' exclusion, but the scenario coverage is strong enough that an agent knows when to reach for it.

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