Skip to main content
Glama
trustxai
by trustxai

airbyte_get_job

Read-onlyIdempotent

Retrieve full details of a sync or reset job by its numeric ID, including status, duration, and volume metrics.

Instructions

Get full details of a single sync or reset job by its numeric ID.

Returns the job status, type, associated connection, start time, duration, and volume metrics (bytes and rows synced). Use this to inspect a specific job's outcome.

When to Use: - Check whether a specific job succeeded or failed. - Get precise bytes/rows synced for a particular run. - Inspect job duration for performance analysis. - Follow up on a job ID returned by airbyte_list_jobs.

When NOT to Use: - If you need to browse multiple jobs, use airbyte_list_jobs with filters. - To see the pipeline definition (schedule, streams), use airbyte_get_connection instead.

Returns: Job details including: jobId, jobType, status, connectionId, startTime, duration, bytesSynced, rowsSynced.

Markdown format renders a heading with bullet-point fields.
JSON format returns the full API response object.

Examples: Get job by ID: params = { "job_id": "12345" } Get raw JSON: params = { "job_id": "12345", "response_format": "json" }

Error Handling: Returns a 404 message if the job ID does not exist.

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, destructiveHint, idempotentHint), the description discloses return fields (status, type, connection, duration, metrics) and error handling (404 for missing ID), adding valuable behavioral context 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?

The description is well-structured with clear sections, front-loads the main purpose, and each sentence adds value. Slightly verbose but appropriate for the detail level.

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 and comprehensive annotations, the description covers all necessary context: purpose, usage, parameters, return values, examples, and error handling. Complete for an agent to use correctly.

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?

Though schema description coverage is reported as 0%, the description provides example usage and clarifies that job_id is a numeric ID as string and response_format has a default. This adds practical semantics beyond the schema.

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 'Get full details of a single sync or reset job by its numeric ID,' specifying the verb, resource, and method. It also distinguishes itself from sibling tools like airbyte_list_jobs and airbyte_get_connection.

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?

The description includes dedicated 'When to Use' and 'When NOT to Use' sections with four use cases and two exclusions that name alternative tools, providing explicit guidance.

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