Skip to main content
Glama
trustxai
by trustxai

airbyte_get_job_details

Read-onlyIdempotent

Get detailed job information including per-attempt statistics, failure reasons, and per-stream record counts to diagnose sync failures and monitor job progress.

Instructions

Get detailed job information including per-attempt stats and failure reasons.

Uses the internal Configuration API (POST /v1/jobs/get) which returns much richer data than the public API: full attempt history, per-stream statistics, and structured failure summaries. Works for ALL job types including refresh and clear jobs.

When to Use: - A job failed and you need to understand WHY (failure origin, type, message, stacktrace). - You want per-stream record/byte counts for a specific sync. - You need to see how many attempts a job took and what happened in each one. - Monitor a refresh job's progress (get the job ID from airbyte_trigger_refresh or airbyte_list_jobs_internal).

When NOT to Use: - For a quick status check, use airbyte_get_job (public API). - For actual log lines, use airbyte_get_job_logs or airbyte_get_attempt_logs. - On Airbyte Cloud — use airbyte_get_cloud_sync_logs for full-text logs.

Returns: Job metadata plus a section per attempt with: status, timing, bytes/records synced, per-stream stats, and failure details.

Examples: params = { "job_id": 12345 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint false), description reveals it uses internal Configuration API (POST /v1/jobs/get), works for ALL job types, and returns richer data than public API. No contradictions.

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-structured with clear headings and bullet points. Concise yet comprehensive, every sentence adds value. Efficient length.

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?

Given the tool's simplicity (one required parameter), presence of output schema, and comprehensive annotations, the description covers all necessary aspects: purpose, usage guidance, return value summary, and alternatives.

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?

With 0% schema description coverage (per context), the description only provides an example parameter object but no explicit explanation of job_id or response_format fields. Partially compensates but could be more thorough.

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?

Description clearly states it gets detailed job information with per-attempt stats and failure reasons, using internal API. Distinguishes from sibling tools like airbyte_get_job (public API) and airbyte_get_job_logs by noting the richer data and specific use case.

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?

Contains explicit 'When to Use' and 'When NOT to Use' sections, listing concrete scenarios (e.g., job failure analysis, per-stream stats) and alternative tools per case. Includes a parameter example.

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