Skip to main content
Glama
trustxai
by trustxai

airbyte_update_connection

Idempotent

Modify any aspect of an Airbyte connection with partial updates: change schedule, enable/disable, adjust streams, or update namespace settings.

Instructions

Update an existing connection's configuration.

Uses PATCH semantics: only the fields you provide are changed.

When to Use: - Change a connection's schedule (e.g. from daily to hourly). - Enable/disable a connection by changing its status. - Add or remove streams from the sync. - Update namespace or prefix settings.

Recommended Workflow: 1. Call airbyte_get_connection to see the current configuration. 2. Build the update payload with only the fields to change. 3. Call this tool.

Returns: The updated connection details.

Examples: Pause a connection: params = { "connection_id": "...", "status": "inactive" } Change schedule: params = { "connection_id": "...", "schedule": { "scheduleType": "basic", "basicTiming": "Every 6 hours" } }

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 indicate readOnlyHint=false (mutation) and destructiveHint=false. Description adds PATCH semantics (only provided fields change) and mentions return value. No contradictions.

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: brief intro, PATCH note, 'When to Use' list, recommended workflow, 'Returns', and examples. Every sentence is relevant and concise.

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 rich input schema descriptions and presence of output schema, description covers all key aspects: purpose, usage guidance, workflow, and examples. Complete for an update tool.

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?

Schema description coverage is 0% but input schema has descriptions for each parameter. The description provides no parameter details but gives examples showing how to use status and schedule, adding some value. Adequate but not fully compensatory.

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 'Update an existing connection's configuration' and specifies PATCH semantics. It distinguishes itself from siblings like airbyte_create_connection (creation) and airbyte_get_connection (read-only).

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 lists when to use (change schedule, enable/disable, add/remove streams, update namespace/prefix) and provides a recommended workflow with three steps. Also includes examples for common use cases.

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