Skip to main content
Glama
trustxai
by trustxai

airbyte_get_job_details

Read-onlyIdempotent

Retrieve detailed job information with per-attempt stats and failure reasons. Use to understand why a job failed or view per-stream record counts.

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.

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.

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 (internal API not available).

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?

Annotations already provide safety hints, but the description adds important context: it uses the internal API, returns richer data than public API, and is not available on Airbyte Cloud. 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 front-loaded purpose, clear sections, and an example. Every sentence adds value with no redundancy.

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 output schema exists, the description does not need to detail return values. It covers usage, alternatives, limitations, and expected output, making it complete.

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?

Only one required parameter (job_id) with a schema description, so the description does not need to add much. It adds no extra parameter details beyond the schema, which is adequate.

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 the tool gets detailed job information including per-attempt stats and failure reasons, and distinguishes it from siblings by noting it uses the internal API for richer data.

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 provide clear criteria and name alternative tools (airbyte_get_job, airbyte_get_job_logs, etc.) for other use cases.

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