datanika-mcp

create_pipeline

Set up a new dbt transformation pipeline by specifying its name, destination connection, and optional dbt command (run, build, test, seed, snapshot, compile).

Instructions

Create a new pipeline (dbt transform orchestration).

Write tool: available only when this session was granted write access — the local server's --allow-write flag, or an OAuth consent in which the user approved write. Read-only sessions refuse it.

Args: name: Pipeline name. destination_connection_id: ID of the destination connection. command: dbt command — 'run', 'build', 'test', 'seed', 'snapshot', 'compile'. description: Optional description.

Input Schema

TableJSON Schema

Name	Required	Default
`name`	Yes
`command`	No	run
`description`	No
`destination_connection_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 17, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the burden and discloses the critical authorization behavior and that read-only sessions will refuse the call. It does not discuss side effects or duplicate handling, but 'create' and the access warning cover the main non-obvious behavior.

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?

The description leads with the purpose, adds one necessary access-control note, and then uses a compact Args block. Every sentence contributes; no filler or duplication beyond the useful args list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create operation with an output schema, this covers the operation, required access mode, and all argument meanings. The only gap is a brief pointer to sibling tools like trigger_pipeline when the intent is to execute rather than create.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All four parameters are listed, and command gains real value by enumerating allowed dbt commands ('run', 'build', 'test', 'seed', 'snapshot', 'compile'). However, name, destination_connection_id, and description mostly restate schema titles/defaults rather than adding deeper semantics.

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 first sentence states a specific verb ('Create') and resource ('new pipeline') and clarifies 'dbt transform orchestration,' distinguishing it from siblings like create_transformation. The purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly frames this as a write tool, states it is available only with --allow-write or OAuth write consent, and warns read-only sessions refuse it. It gives clear access context but does not name alternative tools or when to prefer triggering an existing pipeline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.