Skip to main content
Glama
trustxai
by trustxai

airbyte_list_jobs_internal

Read-onlyIdempotent

Retrieve complete job history for a connection, including refresh and clear jobs not visible in the public API.

Instructions

List ALL job types for a connection, including refresh and clear.

Uses the internal Configuration API (POST /v1/jobs/list) which returns every job type: sync, reset_connection, refresh, clear, and more. The public API's airbyte_list_jobs only returns sync and reset on most Airbyte versions.

When to Use: - Check the status of a refresh job triggered from the UI or via airbyte_trigger_refresh. - See clear jobs that aren't visible in the public API. - Get a complete job history for a connection including all job types. - Monitor a running refresh to see if it has completed.

When NOT to Use: - On Airbyte Cloud — use airbyte_get_cloud_sync_logs for full-text logs. - If you only need sync/reset jobs, airbyte_list_jobs is simpler and works on Cloud too.

Config Types (filter): Common values for config_types: - "sync" — regular incremental or full-refresh syncs - "reset_connection" — connection resets - "refresh" — stream refreshes (merge or truncate) - "clear" — stream clears When omitted, returns ALL types.

Returns: Paginated list of jobs with per-attempt stats. Each entry shows config type, status, timestamps, and stream-level record counts when available.

Examples: All jobs for a connection: params = { "connection_id": "a1b2c3d4-..." } Only refresh jobs: params = { "connection_id": "a1b2c3d4-...", "config_types": ["refresh"] } Failed jobs of any type: params = { "connection_id": "a1b2c3d4-...", "status": "failed" }

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?

Discloses use of internal Configuration API, pagination, per-attempt stats, config types filter. Annotations already declare readOnly, idempotent, non-destructive; description adds meaningful 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections: overview, when to use/not use, config types, returns, examples. Concise at ~200 words, every sentence adds value.

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?

Comprehensive for a list tool with output schema. Covers purpose, usage criteria, parameter details, return structure, and examples. No gaps given the complexity and available structured fields.

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?

Schema has descriptions for all parameters (high coverage), but the tool description adds value by explaining config_types common values and providing examples with parameter usage. Baseline 3, +1 for practical usage guidance.

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 ALL job types via internal API, explicitly distinguishing from sibling airbyte_list_jobs which only returns sync/reset. Specific verb 'list', resource 'jobs', and scope 'all types'.

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?

Explicitly provides when-to-use (checking refresh/clear jobs, complete history) and when-not-to-use (Airbyte Cloud, only sync/reset needed). Names alternatives airbyte_get_cloud_sync_logs and airbyte_list_jobs.

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