Skip to main content
Glama
trustxai
by trustxai

airbyte_wait_for_job

Read-onlyIdempotent

Poll an Airbyte job until it completes or times out, returning the final status. Use after triggering a job to wait for completion.

Instructions

Poll an internal job until it reaches a terminal status.

Uses the internal Configuration API (POST /jobs/get) to poll job status until it becomes succeeded, failed, cancelled, or incomplete, or until max_wait_seconds is reached.

When to Use: - After airbyte_trigger_refresh or airbyte_trigger_clear to block until the job finishes. - Automate workflows that need to know when a job completed.

When NOT to Use: - For a one-shot status check, use airbyte_get_job_details. - On Airbyte Cloud (internal API not available).

Returns: Final job summary when a terminal status is reached, or a timeout message if max_wait_seconds elapses first.

Examples: Wait up to 10 minutes for job 12345: params = { "job_id": 12345, "max_wait_seconds": 600 } Poll every 10 seconds: params = { "job_id": 12345, "poll_interval_seconds": 10 }

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 declare readOnlyHint=true and idempotentHint=true, so no contradiction. Description adds valuable behavioral context: uses POST /jobs/get, polls until succeeded/failed/cancelled/incomplete or timeout, returns final summary or timeout message. No missing critical behavior.

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?

Concise and well-structured with clear sections (intro, when to use/not use, returns, examples). Every sentence adds value with no repetition or fluff.

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?

Tool is a polling wrapper with timeout; description covers purpose, usage, constraints, return behavior, and examples. Output exists (implied by 'Returns final job summary'), but not detailed. Still complete for the tool's complexity.

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?

Input schema has 100% description coverage for all four parameters (job_id, response_format, max_wait_seconds, poll_interval_seconds). Description adds no additional parameter semantics beyond examples, so baseline 3 applies.

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 'Poll an internal job until it reaches a terminal status.' It uses specific verb (poll) and resource (internal job), and distinguishes from siblings like airbyte_get_job_details which is a one-shot check.

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 sections for when to use (after trigger_refresh/trigger_clear) and when NOT to use (for one-shot status check or on Airbyte Cloud). Also names alternative tool airbyte_get_job_details.

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