Skip to main content
Glama

transfer_all_assets

Move all assets from one user to another with structured input, ensuring streamlined ownership transitions.

Instructions

Transfer all assets from one user to another

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
new_owner_idYes
user_idYes

Implementation Reference

  • Core implementation of the transfer_all_assets tool in AYXMCPTools class. Transfers user assets (workflows, schedules, collections) to a new owner using the Alteryx API.
    def transfer_all_assets( self, user_id: str, new_owner_id: str, transfer_workflows: bool, transfer_schedules: bool, transfer_collections: bool, ): """Transfer all assets (workflows, schedules, collections) owned by one user to another.""" try: user = self.users_api.users_get_user(user_id) if not user: return "Error: User 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.TransferUserAssetsContract( owner_id=new_owner_id, transfer_workflows=transfer_workflows, transfer_schedules=transfer_schedules, transfer_collections=transfer_collections, ) api_response = self.users_api.users_transfer_assets(user_id, contract) return pprint.pformat(api_response) except ApiException as e: return f"Error: {e}"
  • MCP tool registration and thin handler wrapper that delegates to the tools implementation.
    @self.app.tool() def transfer_all_assets(user_id: str, new_owner_id: str): """Transfer all assets from one user to another""" return self.tools.transfer_all_assets(user_id, new_owner_id)
  • Tool description and name listed in the MCP server prompt documentation.
    - transfer_all_assets: Transfer all user assets

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