Skip to main content
Glama
trustxai
by trustxai

airbyte_get_attempt_logs

Read-onlyIdempotent

Retrieve structured logs for a specific job attempt to debug failures efficiently. Returns JSON with attempt metadata and log entries.

Instructions

Get logs for a specific attempt of a job.

Uses the internal Configuration API (POST /v1/attempt/get_for_job) to fetch structured log entries for exactly one attempt. More efficient than airbyte_get_job_logs when you know which attempt failed.

Always returns JSON — structured logs are best consumed as-is.

When to Use: - A job had multiple attempts and you want logs for a specific one (e.g. the failing attempt). - You already identified the failing attempt number from airbyte_get_job_details.

When NOT to Use: - If you want logs for all attempts, use airbyte_get_job_logs. - On Airbyte Cloud — use airbyte_get_cloud_sync_logs for full-text logs.

Returns: JSON with attempt metadata and structured log entries, truncated to the last tail_lines entries.

Examples: params = { "job_id": 12345, "attempt_number": 0 } params = { "job_id": 12345, "attempt_number": 2, "tail_lines": 500 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds efficiency details, truncation behavior, and return format (JSON, structured). Adds value beyond annotations without contradiction.

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?

Well-structured with sections and bullet points. Front-loaded with main purpose, then usage guidelines, return description, and examples. Slightly verbose but 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?

Tool has 3 params, no nested objects, and an output schema. Description covers return format, truncation, contrasts with siblings, and provides examples. Complete and self-contained.

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

Parameters4/5

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

Input schema already describes parameters well (100% coverage). Description adds examples and explains when to use tail_lines, providing context beyond schema. Baseline 3 plus extra value.

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?

Clearly states it gets logs for a specific attempt of a job, mentions the internal API endpoint, and distinguishes from sibling airbyte_get_job_logs. Specific verb+resource with scope.

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

Usage Guidelines5/5

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

Explicit 'When to Use' and 'When NOT to Use' sections, naming specific alternatives (airbyte_get_job_logs, airbyte_get_cloud_sync_logs). Provides clear context for 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/trustxai/airbyte-mcp'

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