Skip to main content
Glama
trustxai
by trustxai

airbyte_create_source

Create a new source connector to define where Airbyte reads data. Configure connections to databases, APIs, or SaaS apps for data ingestion.

Instructions

Create a new source connector in Airbyte.

A source defines where Airbyte reads data from (a database, API, SaaS app, etc.). Each source type requires its own configuration schema (e.g. host, port, credentials for Postgres).

When to Use: - Set up a brand-new data source inside a workspace. - Automate provisioning of sources as part of a pipeline setup.

Recommended Workflow: 1. Call airbyte_list_source_definitions to find the definition ID for the connector type you want (e.g. "source-postgres"). 2. Review an existing source of the same type with airbyte_get_source to understand the configuration structure. 3. Call this tool with the appropriate configuration.

Returns: The created source details (same fields as airbyte_get_source).

Examples: params = { "name": "Production Postgres", "workspace_id": "a1b2c3d4-...", "definition_id": "decd338e-...", "configuration": { "sourceType": "postgres", "host": "db.example.com", "port": 5432, "database": "mydb", "username": "readonly", "password": "secret" } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description doesn't need to restate those. It adds behavioral context by noting the return value and suggesting a workflow, but doesn't explicitly address potential side effects (e.g., credential storage, costing) or describe the creation behavior beyond the basic fact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is well-structured with clear sections (introduction, when to use, workflow, returns, examples). It is somewhat lengthy but each part serves a purpose. The front-loaded purpose sentence is effective.

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 tool's complexity (multiple parameters, dynamic configuration schema) and the presence of an output schema (so return format isn't needed in description), the description covers all essential aspects: purpose, usage guidance, workflow, parameter meaning via examples, and return value. It references sibling tools appropriately.

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?

Despite the context stating 0% schema description coverage, the actual input schema includes descriptions for most parameters (name, workspace_id, definition_id, configuration, secret_id). The description adds value beyond the schema by providing an example with typical fields and a workflow hint to look at existing sources for configuration structure.

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 explicitly states 'Create a new source connector in Airbyte' and explains what a source is (a data source like database, API, etc.). It distinguishes from sibling tools like airbyte_list_sources or airbyte_update_source by focusing solely on creation.

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 'When to Use' section provides two clear use cases (set up new source, automate provisioning). It also includes a recommended workflow with steps referencing sibling tools, but lacks explicit when-not-to-use or alternative tools that might be more appropriate in some scenarios.

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