Skip to main content
Glama
trustxai
by trustxai

airbyte_list_jobs

Read-onlyIdempotent

List sync and reset jobs with filters for connection, workspace, status, and date range. Use to monitor sync activity, troubleshoot failures, and audit sync volume.

Instructions

List sync and reset jobs with rich filtering options.

Jobs represent individual sync or reset executions. Every time a connection runs (manually or on schedule), Airbyte creates a job that tracks status, duration, bytes synced, and rows synced.

When to Use: - Check recent sync activity for a specific connection. - Find failed or running jobs across workspaces. - Audit sync volume (bytes/rows) over a date range. - Monitor whether scheduled syncs are executing on time.

When NOT to Use: - If you already have a job ID, use airbyte_get_job for full details. - To see pipeline definitions (schedule, streams), use airbyte_get_connection instead.

Filters: All filters are optional and combinable: - connection_id: restrict to one pipeline. - workspace_ids: restrict to specific workspaces. - job_type: "sync" or "reset". - status: pending, running, incomplete, failed, succeeded, or cancelled. - created_at_start / created_at_end: ISO-8601 date range (e.g. "2024-01-01T00:00:00Z"). - order_by: sort field, e.g. "createdAt|DESC" (default).

Returns: Paginated list of jobs. Each entry includes: - jobId, jobType, status, connectionId, startTime, duration, bytesSynced, rowsSynced.

Markdown format shows a heading per job with bullet fields.
JSON format returns the raw API response array.

Pagination: Use limit (1–100, default 20) and offset (default 0).

Examples: Recent failed jobs for a connection: params = { "connection_id": "a1b2c3d4-...", "status": "failed", "limit": 5 } All sync jobs in the last 7 days: params = { "job_type": "sync", "created_at_start": "2024-06-01T00:00:00Z" } Latest 3 jobs, newest first: params = { "limit": 3, "order_by": "createdAt|DESC" }

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 declare read-only, but description adds details on pagination, response format (markdown/json), and returned fields, beyond annotations.

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, but slightly lengthy due to examples and detailed explanations. Still appropriate for the tool's complexity.

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?

Covers all aspects: purpose, when to use, parameters, return format, pagination, and examples. No gaps given the annotations and output schema.

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

Parameters5/5

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

Description explains every filter with examples, default values, and combinability. Schema descriptions are minimal, but the description fully compensates with rich parameter semantics.

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 lists sync and reset jobs with rich filtering. Differentiates from siblings like airbyte_get_job and airbyte_get_connection by explicitly stating when to use which.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections with concrete scenarios and references to alternative tools.

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