Skip to main content
Glama
trustxai
by trustxai

airbyte_create_destination

Define a data destination in Airbyte for writing to warehouses, databases, or data lakes, enabling automated pipeline provisioning.

Instructions

Create a new destination connector in Airbyte.

A destination defines where Airbyte writes data to (a warehouse, database, data lake, SaaS tool, etc.). Each destination type requires its own configuration schema.

When to Use: - Set up a brand-new data destination inside a workspace. - Automate provisioning of destinations for pipeline setup.

Recommended Workflow: 1. Call airbyte_list_destination_definitions to find the definition ID for the connector type you want. 2. Review an existing destination of the same type with airbyte_get_destination to understand the config structure. 3. Call this tool with the appropriate configuration.

Returns: The created destination details.

Examples: params = { "name": "Analytics Warehouse", "workspace_id": "a1b2c3d4-...", "definition_id": "22f6c74f-...", "configuration": { "destinationType": "bigquery", "project_id": "my-project", "dataset_id": "raw_data", "credentials_json": "..." } }

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 are basic (readOnlyHint=false, etc.). Description adds context like requiring configuration schema and the creation workflow. Does not contradict annotations. Could mention idempotency or duplicate handling but not necessary.

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?

Description is well-structured with clear sections, front-loaded purpose, and every sentence adds value. Not overly verbose.

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 (single param that is an object with sub-properties) and presence of an output schema, the description provides a complete workflow, examples, and return details. Sufficient for an agent to understand and use the tool.

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?

Schema already has descriptions for all parameters (name, workspace_id, definition_id, configuration, response_format). Description adds extra context with workflow steps and an example, enhancing understanding, especially for the open-ended configuration object.

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 'Create a new destination connector' with a verb and resource. Explains what a destination is and distinguishes from sibling tools like airbyte_create_source.

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 provides 'When to Use' section with two specific scenarios and a 'Recommended Workflow' that references other tools (list_destination_definitions, get_destination), giving clear guidance and alternatives.

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