Skip to main content
Glama
fivetran

Fivetran MCP Server

Official
by fivetran

create_group

Create a new group in your Fivetran account, required before adding a destination.

Instructions

⚠️ WRITE OPERATION - Confirm with user before calling. Creates a new group in your Fivetran account. > IMPORTANT: Groups and destinations are mapped 1:1 to each other. We do this mapping using the group's id value that we automatically generate when you create a group, and the destination's group_id value that you specify when you create a destination. This means that you must create a group in your Fivetran account before you can create a destination in it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schema_fileYesREQUIRED: You must first read the schema file at 'open-api-definitions/groups/create_group.json', then provide this exact path here to confirm.
request_bodyYesJSON string containing the request body. Refer to the schema file for the expected structure.
Behavior4/5

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

No annotations provided, so description carries full burden. It explicitly flags as a write operation, warns to confirm with user, and explains the critical mapping dependency. Could mention irreversibility.

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?

Front-loaded with warning and purpose. The mapping explanation is verbose but necessary. Could be slightly more concise.

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?

Covers operation, prerequisites, and mapping. Lacks output return details but no output schema exists. Adequate for a simple creation tool.

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?

Schema coverage is 100% with detailed parameter descriptions. The description adds value by explaining the reason for the schema_file parameter (to confirm) and the mapping logic.

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 creates a new group in Fivetran, with specific verb and resource. It distinguishes from sibling creation tools by explaining the group-to-destination mapping.

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?

Provides context that groups are prerequisite for destinations, but lacks explicit alternatives or when-not-to-use 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/fivetran/fivetran-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server