Skip to main content
Glama
trustxai
by trustxai

airbyte_list_sources

Read-onlyIdempotent

List configured source connectors in an Airbyte workspace. Retrieve source names, IDs, types, and creation dates with pagination and workspace filtering.

Instructions

List source connectors configured in Airbyte.

Sources represent the data origins (databases, APIs, SaaS apps, etc.) that Airbyte reads from. Each source is linked to a workspace and can be paired with one or more destinations via connections.

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

When NOT to Use: - If you already have a source ID, use airbyte_get_source for full details. - To see what data a source actually moves, look at connections (airbyte_list_connections) or jobs (airbyte_list_jobs).

Returns: Paginated list of sources. Each entry includes: - name, sourceId (UUID), sourceType, workspaceId, createdAt.

Markdown format shows a heading per source 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 sources in a workspace: params = { "workspace_ids": ["a1b2c3d4-..."] } List first 5 sources across all workspaces: params = { "limit": 5 } Include soft-deleted sources: params = { "include_deleted": true }

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 already declare readOnlyHint=true, destructiveHint=false, so description is not needed for safety. However, description adds pagination behavior, response format options, and the ability to include deleted sources. No contradictions. Minor gap: no mention of rate limits or error conditions.

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 clear sections (When to Use, When NOT to Use, Returns, Pagination, Examples). No fluff, every sentence adds value. Front-loaded with purpose.

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 sibling tools and parameters, the description is complete. It explains return fields (name, sourceId, etc.) and pagination. An output schema exists but description covers what the agent needs.

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 low schema description coverage (0%), the tool description thoroughly explains parameters: limit (1-100, default 20), offset (default 0), workspace_ids, include_deleted, response_format. Examples show typical usage. Compensates fully for missing schema descriptions.

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?

Description clearly states 'List source connectors configured in Airbyte' and distinguishes from siblings like airbyte_get_source, airbyte_list_connections, and airbyte_list_jobs. It is specific about what the tool does and the resource.

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?

Has explicit 'When to Use' and 'When NOT to Use' sections, providing clear context. It tells when to use this tool (discover sources, find UUIDs) and when to use alternatives (get_source, list_connections, list_jobs). Examples further clarify usage.

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