Skip to main content
Glama
trustxai
by trustxai

airbyte_get_source

Read-onlyIdempotent

Retrieve full details of a source connector by its UUID, including name, type, workspace, creation date, and configuration with secrets masked.

Instructions

Get full details of a single source connector by its UUID.

Returns the source name, type (e.g. postgres, stripe, google-sheets), workspace, creation date, and connector configuration. Secrets in the configuration object are masked by the Airbyte API.

When to Use: - Inspect a specific source's configuration or connector type. - Verify a source ID is valid. - Check when a source was created or which workspace owns it.

When NOT to Use: - If you need to browse sources, use airbyte_list_sources. - To see sync activity, use airbyte_list_jobs filtered by the connection that uses this source.

Returns: Source details including: name, sourceId, sourceType, workspaceId, createdAt, and configuration (secrets masked).

Markdown format renders a heading with bullet-point fields.
JSON format returns the full API response object.

Examples: Get source by ID: params = { "source_id": "a1b2c3d4-..." } Get raw JSON: params = { "source_id": "a1b2c3d4-...", "response_format": "json" }

Error Handling: Returns a 404 message if the source ID does not exist.

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?

Discloses secret masking, 404 error handling, and response format options. Annotations already declare safety, and the description adds relevant behavioral context without contradiction.

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?

Well-structured with sections, but some redundancy (e.g., 'Returns' repeats earlier info). Still efficient and easy to read.

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?

Covers purpose, parameters, return values (with output schema present), error handling, and usage guidance completely.

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 0% schema coverage, the description explains both parameters (source_id and response_format) with examples and default values, effectively compensating.

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 it retrieves full details of a single source connector by UUID, and lists returned fields. It distinguishes from sibling tools like airbyte_list_sources.

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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, with alternatives such as airbyte_list_sources and airbyte_list_jobs.

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