Skip to main content
Glama
andrewkkchan

MCP Fivetran

by andrewkkchan

list_connections

Retrieve all connection IDs from your Fivetran account to manage data pipelines and monitor integration status.

Instructions

Tool for listing all connections' IDs in the Fivetran account.

This tool retrieves all connection IDs from the Fivetran account by making a GET request
to the Fivetran API. It requires an authentication token stored in the auth_token variable.

Returns:
    str: A comma-separated string of all connection IDs in the account.

Note:
    The auth_token must be set before calling this function.
    The function does not handle exceptions that might occur during the API request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the list_connections tool. It makes a GET request to the Fivetran API to retrieve all connections and returns a comma-separated string of connection IDs.
    @mcp.tool()
    def list_connections() -> str:
        """Tool for listing all connections' IDs in the Fivetran account.
    
        This tool retrieves all connection IDs from the Fivetran account by making a GET request
        to the Fivetran API. It requires an authentication token stored in the auth_token variable.
    
        Returns:
            str: A comma-separated string of all connection IDs in the account.
    
        Note:
            The auth_token must be set before calling this function.
            The function does not handle exceptions that might occur during the API request.
        """
    
        url = "https://api.fivetran.com/v1/connections"
    
        response = requests.request("GET", url, headers=headers)
    
        data = json.loads(response.text)
    
        item_ids = [item["id"] for item in data["data"]["items"]]
    
        return ", ".join(item_ids)
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about authentication requirements ('auth_token must be set'), API interaction ('making a GET request to the Fivetran API'), and error handling ('does not handle exceptions'). However, it doesn't mention rate limits, pagination, or what happens when no connections exist.

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?

The description is well-structured with clear sections (description, returns, note) and avoids redundancy. However, the 'Returns' section could be more concise, and some information about authentication could be integrated more smoothly. Overall, most sentences earn their place.

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?

Given the tool has 0 parameters, an output schema exists, and no annotations, the description provides good contextual completeness. It explains what the tool does, authentication requirements, return format, and exception handling limitations. The main gap is lack of guidance on when to use this versus other tools.

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?

The tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on authentication and behavioral aspects.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'listing all connections' IDs in the Fivetran account' and 'retrieves all connection IDs from the Fivetran account'. It specifies the verb (list/retrieve) and resource (connection IDs), though it doesn't explicitly differentiate from sibling tools like 'sync_connection' which likely performs a different action.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions authentication requirements and exception handling, but doesn't indicate scenarios where this tool is preferred over other tools or when it should be avoided. No explicit when/when-not/alternatives are provided.

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/andrewkkchan/mcp_fivetran'

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