Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

add_workflow_to_collection

Add a workflow to an Alteryx collection using workflow and collection IDs to organize and manage analytics processes.

Instructions

Add a workflow to a collection by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collection_idYes
workflow_idYes

Implementation Reference

  • Core handler implementation that checks if collection and workflow exist, creates an AddWorkflowContract, calls the Alteryx API to add the workflow to the collection, and formats the response.
    def add_workflow_to_collection(self, collection_id: str, workflow_id: str):
        """Add a workflow to a collection by its ID"""
        try:
            collection = self.collections_api.collections_get_collection(collection_id)
            if not collection:
                return "Error: Collection not found"
            workflow = self.workflows_api.workflows_get_workflow(workflow_id)
            if not workflow:
                return "Error: Workflow not found"
            contract = server_client.AddWorkflowContract(workflow_id=workflow_id)
            api_response = self.collections_api.collections_add_workflow_to_collection(collection_id, contract)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration using @self.app.tool() decorator. This wrapper function delegates the call to the underlying tools.add_workflow_to_collection method.
    @self.app.tool()
    def add_workflow_to_collection(collection_id: str, workflow_id: str):
        """Add a workflow to a collection by its ID"""
        return self.tools.add_workflow_to_collection(collection_id, workflow_id)
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as required permissions, whether this is a mutating operation, error conditions, or what happens if the workflow is already in the collection. This leaves significant gaps for a tool that likely modifies data.

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 is a single, direct sentence with no wasted words, efficiently conveying the core purpose. It's appropriately sized for a simple tool and front-loaded with essential information.

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

Completeness2/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, return values, and error handling, making it inadequate for a tool that likely performs a mutation in a system with many sibling operations.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but adds no parameter details beyond what's implied by the name. It doesn't explain what 'collection_id' and 'workflow_id' represent, their formats, or where to obtain them, failing to address the coverage gap.

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 action ('Add') and target resources ('workflow to a collection'), specifying it's done by ID. It distinguishes from sibling 'remove_workflow_from_collection' by indicating the opposite operation, though it doesn't explicitly differentiate from other collection-related tools like 'add_schedule_to_collection'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., existing collection/workflow), exclusions, or comparisons to similar tools like 'add_schedule_to_collection', leaving the agent to infer usage from context alone.

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/jupiterbak/AYX-MCP-Wrapper'

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