Skip to main content
Glama
trustxai
by trustxai

airbyte_update_source

Idempotent

Update an Airbyte source connector's name or configuration by providing only the fields to change. Use to rotate credentials, rename sources, or adjust settings.

Instructions

Update an existing source connector's name or configuration.

Uses PATCH semantics: only the fields you provide are changed. The configuration object is merged at the top level by the API.

When to Use: - Change connection credentials (e.g. rotate a password). - Rename a source for clarity. - Update connector settings (e.g. change replication slot).

Recommended Workflow: 1. Call airbyte_get_source to see the current configuration. 2. Build the updated configuration with only the changed fields. 3. Call this tool.

Returns: The updated source details.

Examples: Rename a source: params = { "source_id": "a1b2c3d4-...", "name": "New Name" } Update configuration: params = { "source_id": "a1b2c3d4-...", "configuration": { "password": "new-secret" } }

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 indicate idempotentHint=true and non-destructive, but the description adds critical behavioral details: 'Uses PATCH semantics: only the fields you provide are changed. The configuration object is merged at the top level by the API.' This goes beyond annotations and is essential for correct invocation.

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?

The description is well-organized into clear sections: main purpose, PATCH semantics, when to use, recommended workflow, return value, and examples. Every sentence earns its place, and there is no redundant information.

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 complexity of a PATCH update with merging behavior, the description is complete. It covers what the tool does, how it behaves, prerequisites (get source first), and expected outcomes. The presence of an output schema further reduces ambiguity.

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?

Even though the input schema already describes parameters, the description adds significant value by explaining the merge behavior and providing concrete examples (rename and update config). This helps an agent understand how to construct the configuration object correctly.

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 the tool updates an existing source connector's name or configuration, using specific verb and resource. It differentiates it from sibling update tools like airbyte_update_connection or airbyte_update_destination by focusing on sources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'When to Use' bullet points (change credentials, rename, update settings) and a 'Recommended Workflow' with three steps. It does not explicitly state when not to use, but the context given is sufficient for an agent to decide.

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