Skip to main content
Glama
trustxai
by trustxai

airbyte_get_destination

Read-onlyIdempotent

Inspect a specific destination connector by providing its UUID to obtain name, connector type, workspace, creation date, and configuration with masked secrets.

Instructions

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

Returns the destination name, type (e.g. bigquery, snowflake, s3), workspace, creation date, and connector configuration. Secrets in the configuration object are masked by the Airbyte API.

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

When NOT to Use: - If you need to browse destinations, use airbyte_list_destinations. - To see sync activity targeting this destination, use airbyte_list_jobs filtered by the relevant connection.

Returns: Destination details including: name, destinationId, destinationType, 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 destination by ID: params = { "destination_id": "a1b2c3d4-..." } Get raw JSON: params = { "destination_id": "a1b2c3d4-...", "response_format": "json" }

Error Handling: Returns a 404 message if the destination 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?

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds valuable context: secrets are masked, 404 error handling, and response format details. No contradictions.

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 headings (overview, when to use/not use, returns, examples, error handling). Slightly lengthy but every section adds value; no redundant content.

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, usage guidance, error handling, response format, and examples. Output schema exists, so return structure is documented elsewhere. Complete for a read 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 has 2 params (destination_id, response_format) with 0% coverage, but description explains destination_id as UUID, response_format as enum (markdown/json), and includes examples. Fully compensates for lack of 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 'Get full details of a single destination connector by its UUID' and lists returned fields (name, type, workspace, etc.). Differentiates from sibling tools like airbyte_list_destinations and airbyte_list_jobs.

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 with specific alternative tools (airbyte_list_destinations, airbyte_list_jobs). Provides clear decision guidance.

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