Skip to main content
Glama
trustxai
by trustxai

airbyte_trigger_sync

Trigger a sync or reset job for an Airbyte connection to replicate data or clear and re-sync. Use to manually start jobs outside schedule or after schema changes.

Instructions

Trigger a sync or reset job for a connection.

Starts a new job that replicates data from source to destination (sync) or clears destination data and re-syncs (reset).

When to Use: - Manually kick off a sync outside the regular schedule. - Trigger a reset after schema changes or data issues. - Automate syncs in response to upstream events.

When NOT to Use: - The connection is already running a sync (check with airbyte_list_jobs first).

Returns: The newly created job with its jobId and initial status.

Examples: Trigger a sync: params = { "connection_id": "a1b2c3d4-..." } Trigger a reset: params = { "connection_id": "a1b2c3d4-...", "job_type": "reset" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description explains reset clears destination data, which contradicts destructiveHint=false annotation. This is a serious inconsistency.

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-organized with sections, bullet points, and examples. No unnecessary text, every sentence adds value.

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?

Mentions return of jobId and status, but could elaborate on job object. Adequate given output schema existence.

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?

Adds examples and clarifies sync vs reset beyond schema descriptions. Schema itself covers connection_id and job_type well.

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 triggers sync or reset jobs for a connection, replicating data or clearing then re-syncing. Distinguishes from sibling listing/update tools by focusing on job execution.

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, including checking for running jobs. Provides examples for sync and reset.

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