Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

transfer_workflow

Transfer ownership of Alteryx workflows to different users by specifying workflow and new owner IDs.

Instructions

Transfer workflow ownership to a new user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes
new_owner_idYes

Implementation Reference

  • MCP tool registration for 'transfer_workflow'. The @self.app.tool() decorator registers this thin handler function with the MCP server, which delegates execution to the Tools class method.
    @self.app.tool()
    def transfer_workflow(workflow_id: str, new_owner_id: str):
        """Transfer workflow ownership to a new user"""
        return self.tools.transfer_workflow(workflow_id, new_owner_id)
  • Core handler logic in the Tools class. Validates the workflow and new owner exist, creates TransferWorkflowContract, calls the Alteryx Server API to transfer ownership, and formats the response.
    def transfer_workflow(self, workflow_id: str, new_owner_id: str):
        """Transfer a workflow to a new owner by its ID"""
        try:
            workflow = self.workflows_api.workflows_get_workflow(workflow_id)
            if not workflow:
                return "Error: Workflow not found"
            new_owner = self.users_api.users_get_user(new_owner_id)
            if not new_owner:
                return "Error: New owner not found"
            contract = server_client.TransferWorkflowContract(owner_id=new_owner_id)
            api_response = self.workflows_api.workflows_transfer_workflow(workflow_id, contract)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • Swagger-generated schema/model for TransferWorkflowContract, used as the request body for the workflows_transfer_workflow API call. Defines owner_id (required) and transfer_schedules.
    class TransferWorkflowContract(object):
        """NOTE: This class is auto generated by the swagger code generator program.
    
        Do not edit the class manually.
        """
    
        """
        Attributes:
          swagger_types (dict): The key is attribute name
                                and the value is attribute type.
          attribute_map (dict): The key is attribute name
                                and the value is json key in definition.
        """
        swagger_types = {"owner_id": "str", "transfer_schedules": "bool"}
    
        attribute_map = {"owner_id": "ownerId", "transfer_schedules": "transferSchedules"}
    
        def __init__(self, owner_id=None, transfer_schedules=None, _configuration=None):  # noqa: E501
            """TransferWorkflowContract - a model defined in Swagger"""  # noqa: E501
            if _configuration is None:
                _configuration = Configuration()
            self._configuration = _configuration
    
            self._owner_id = None
            self._transfer_schedules = None
            self.discriminator = None
    
            self.owner_id = owner_id
            self.transfer_schedules = transfer_schedules
    
        @property
        def owner_id(self):
            """Gets the owner_id of this TransferWorkflowContract.  # noqa: E501
    
    
            :return: The owner_id of this TransferWorkflowContract.  # noqa: E501
            :rtype: str
            """
            return self._owner_id
    
        @owner_id.setter
        def owner_id(self, owner_id):
            """Sets the owner_id of this TransferWorkflowContract.
    
    
            :param owner_id: The owner_id of this TransferWorkflowContract.  # noqa: E501
            :type: str
            """
            if self._configuration.client_side_validation and owner_id is None:
                raise ValueError("Invalid value for `owner_id`, must not be `None`")  # noqa: E501
    
            self._owner_id = owner_id
    
        @property
        def transfer_schedules(self):
            """Gets the transfer_schedules of this TransferWorkflowContract.  # noqa: E501
    
    
            :return: The transfer_schedules of this TransferWorkflowContract.  # noqa: E501
            :rtype: bool
            """
            return self._transfer_schedules
    
        @transfer_schedules.setter
        def transfer_schedules(self, transfer_schedules):
            """Sets the transfer_schedules of this TransferWorkflowContract.
    
    
            :param transfer_schedules: The transfer_schedules of this TransferWorkflowContract.  # noqa: E501
            :type: bool
            """
            if self._configuration.client_side_validation and transfer_schedules is None:
                raise ValueError("Invalid value for `transfer_schedules`, must not be `None`")  # noqa: E501
    
            self._transfer_schedules = transfer_schedules
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool performs a transfer (implying mutation), but doesn't mention critical details like required permissions, whether the transfer is reversible, effects on existing workflow access, or error conditions. This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded with the 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?

For a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is inadequate. It lacks details on behavior, error handling, permissions, and doesn't compensate for the missing structured information, leaving the agent with insufficient context to use the tool safely and effectively.

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?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'workflow ownership' and 'new user', which loosely maps to the two parameters (workflow_id and new_owner_id), but doesn't explain format, validation, or semantics beyond basic inference. It adds minimal value over the bare schema.

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 ('transfer') and resource ('workflow ownership') with the target ('to a new user'). It distinguishes from siblings like 'change_schedule_owner' by specifying workflow context, but doesn't explicitly contrast with 'transfer_all_assets' which might handle broader transfers.

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 like 'change_schedule_owner' or 'transfer_all_assets'. The description implies it's for transferring workflow ownership specifically, but lacks explicit context about prerequisites, permissions, or scenarios where it's appropriate.

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