Skip to main content
Glama
trustxai
by trustxai

airbyte_create_connection

Creates a connection linking a source to a destination, specifying streams to sync, schedule, and sync modes.

Instructions

Create a new connection (source-to-destination pipeline).

A connection links a source to a destination and defines which streams to sync, the schedule, namespace mapping, and sync modes.

When to Use: - Wire up a new data pipeline between an existing source and destination. - Automate pipeline provisioning.

Recommended Workflow: 1. Ensure the source and destination already exist (or create them with airbyte_create_source / airbyte_create_destination). 2. Call airbyte_get_stream_properties with the sourceId (and optionally destinationId) to discover available streams and their supported sync modes. 3. Build the configurations.streams array and call this tool.

Returns: The created connection details including connectionId.

Examples: Minimal connection: params = { "source_id": "...", "destination_id": "...", "name": "Prod Postgres -> BigQuery" } With schedule and streams: params = { "source_id": "...", "destination_id": "...", "name": "Hourly Sync", "schedule": { "scheduleType": "cron", "cronExpression": "0 * * * *" }, "configurations": { "streams": [ { "name": "users", "syncMode": "incremental_append" }, { "name": "orders", "syncMode": "full_refresh_overwrite" } ] }, "status": "active" }

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 indicate readOnlyHint=false and destructiveHint=false, but description adds context that creation wires up a pipeline and returns connection details. Does not mention potential side effects like immediate sync start, but covers creation behavior adequately.

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 sections, bullet points, and examples. Front-loads the core purpose, then provides workflow and two examples. 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?

Given the input schema richness and presence of output schema, the description covers workflow, examples, and return info. No gaps.

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?

Input schema has extensive descriptions for all parameters (100% coverage), so description only adds examples and context about building the streams array. The description's workflow helps understand parameter use beyond 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 'Create a new connection' and explains it links a source to a destination. It distinguishes from sibling tools like airbyte_create_source and airbyte_create_destination by specifying it's a pipeline between existing connectors.

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?

Has explicit 'When to Use' section and a 'Recommended Workflow' that specifies prerequisites (ensuring source/destination exist, calling airbyte_get_stream_properties). Examples illustrate usage.

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