Skip to main content
Glama

deactivate_schedule

Deactivate a specific schedule by its unique ID using the AYX-MCP-Wrapper server, enabling efficient management of automated workflows and tasks.

Instructions

Deactivate a schedule by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idYes

Implementation Reference

  • The main handler function for the deactivate_schedule tool. It retrieves the current schedule details, constructs an UpdateScheduleContract with enabled set to False, and updates the schedule using the Alteryx server API.
    def deactivate_schedule(self, schedule_id: str): """Deactivate a schedule by its ID""" try: schedule = self.schedules_api.schedules_get_schedule(schedule_id) if not schedule: return "Error: Schedule not found" contract = server_client.UpdateScheduleContract( workflow_id=schedule.workflow_id, owner_id=schedule.owner_id, iteration=schedule.iteration, name=schedule.name, comment=schedule.comment, priority=schedule.priority, worker_tag=schedule.worker_tag, enabled=False, credential_id=schedule.credential_id, time_zone=schedule.time_zone, questions=schedule.questions, ) api_response = self.schedules_api.schedules_update_schedule(schedule_id, contract) return pprint.pformat(api_response) except ApiException as e: return f"Error: {e}"
  • The registration of the deactivate_schedule tool in the MCP server using the @app.tool() decorator. This wrapper delegates the call to the underlying tools instance method.
    @self.app.tool() def deactivate_schedule(schedule_id: str): """Deactivate a schedule by its ID""" return self.tools.deactivate_schedule(schedule_id)

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