Skip to main content
Glama
trustxai
by trustxai

airbyte_list_destinations

Read-onlyIdempotent

List destination connectors in Airbyte workspaces. View names, IDs, types, and creation dates to audit or discover configured data targets.

Instructions

List destination connectors configured in Airbyte.

Destinations represent the data targets (warehouses, databases, lakes, SaaS tools, etc.) that Airbyte writes to. Each destination is linked to a workspace and can receive data from one or more sources via connections.

When to Use: - Discover which destination connectors are set up. - Find a destination's UUID to inspect its configuration or look up related connections. - Audit destinations across one or more workspaces.

When NOT to Use: - If you already have a destination ID, use airbyte_get_destination for full details. - To see what data flows into a destination, look at connections (airbyte_list_connections) or jobs (airbyte_list_jobs).

Returns: Paginated list of destinations. Each entry includes: - name, destinationId (UUID), destinationType, workspaceId, createdAt.

Markdown format shows a heading per destination with bullet
fields. JSON format returns the raw API response array.

Pagination: Use limit (1–100, default 20) and offset (default 0).

Examples: List all destinations in a workspace: params = { "workspace_ids": ["a1b2c3d4-..."] } List first 5 destinations across all workspaces: params = { "limit": 5 } Include soft-deleted destinations: params = { "include_deleted": true }

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?

Adds significant context beyond annotations: pagination details, return format options, soft-deleted inclusion, and examples. No contradiction with readOnlyHint, destructiveHint, idempotentHint.

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, code examples. Every sentence adds value; no fluff. Efficiently front-loaded with purpose and when-to-use.

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?

Comprehensive given 1 required param, optional params, output schema, and annotations. Covers list tool expectations: pagination, filtering, formatting, and example usage.

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?

Despite schema description coverage 0%, the description explains each parameter (workspace_ids, limit, offset, include_deleted, response_format) with context and examples, compensating fully.

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?

Clear verb+resource: 'List destination connectors configured in Airbyte.' Distinguishes from siblings like airbyte_get_destination and airbyte_get_destination_definition by scope and output granularity.

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?

Explicit 'When to Use' and 'When NOT to Use' sections, providing specific alternative tools (airbyte_get_destination, airbyte_list_connections, airbyte_list_jobs) and clear 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