SuperAPI AI Directory

wecom-schedule

General & other

View repository

Updated 10-16 08:41

About this skill

WeCom schedule management skill

wecom_mcp is an MCP tool; all operations are completed by calling this tool.

⚠️ Prerequisites: Before the first call to wecom_mcp , you must follow the wecom-preflight skill to perform the prerequisite check to ensure the tool has been whitelisted.

Interact with the WeCom schedule system through wecom_mcp call schedule <接口名> '<json入参>' .

Notes

  • Schedule list queries only support30 days before and after the current day, time format YYYY-MM-DD or YYYY-MM-DD HH:MM:SS
  • When participant userid is involved, you need to first use the wecom-contact-lookup skill to obtain it; when names are duplicated, display candidates for the user to choose (exposing userid is prohibited)
  • Before creating/modifying/canceling, first confirm the target schedule and participant information
  • errcode != 0 display the error message when ; the returned start_time/end_time is a Unix timestamp (seconds) and needs to be converted to a readable format
  • Pay attention to time format conversion: API input parameters use string format (such as YYYY-MM-DD HH:MM:SS), but the returned values are mostly Unix timestamps and need to be converted when used

API list

get_schedule_list_by_range — query the schedule ID list

Use the wecom_mcp tool to call wecom_mcp call schedule get_schedule_list_by_range '{"start_time": "YYYY-MM-DD HH:MM:SS", "end_time": "YYYY-MM-DD HH:MM:SS"}'

Return the schedule_id_list array. Only supports 30 days before and after the current day.

get_schedule_detail — get schedule details

Use the wecom_mcp tool to call wecom_mcp call schedule get_schedule_detail '{"schedule_id_list": ["SCHEDULE_ID_1", "SCHEDULE_ID_2"]}'

Supports 1~50 IDs, returning schedule title, time, location, participants, etc. See API details。

create_schedule — create a schedule

Use the wecom_mcp tool to call wecom_mcp call schedule create_schedule '{"schedule": {"start_time": "YYYY-MM-DD HH:MM:SS", "end_time": "YYYY-MM-DD HH:MM:SS", "summary": "日程标题", "attendees": [{"userid": "USER_ID"}], "reminders": {"is_remind": 1, "remind_before_event_secs": 3600, "timezone": 8}}}'

See API details | reminders field。

update_schedule — modify a schedule

Only pass in the fields to be modified; fields not passed remain unchanged.

Use the wecom_mcp tool to call wecom_mcp call schedule update_schedule '{"schedule": {"schedule_id": "SCHEDULE_ID", "summary": "更新后的标题"}}'

See API details。

cancel_schedule — cancel a schedule

Use the wecom_mcp tool to call wecom_mcp call schedule cancel_schedule '{"schedule_id": "SCHEDULE_ID"}'

add_schedule_attendees / del_schedule_attendees — manage participants

  • Add participants: use the wecom_mcp tool to call wecom_mcp call schedule add_schedule_attendees '{"schedule_id": "SCHEDULE_ID", "attendees": [{"userid": "USER_ID"}]}'
  • Remove participants: use the wecom_mcp tool to call wecom_mcp call schedule del_schedule_attendees '{"schedule_id": "SCHEDULE_ID", "attendees": [{"userid": "USER_ID"}]}'

check_availablity — query availability

Use the wecom_mcp tool to call wecom_mcp call schedule check_availablity '{"check_user_list": ["USER_ID_1", "USER_ID_2"], "start_time": "YYYY-MM-DD HH:MM:SS", "end_time": "YYYY-MM-DD HH:MM:SS"}'

Supports 1~10 users, returning each user's list of busy periods. See API details。


Typical workflow

Query schedules

Classic query examples:

  • "What schedules do I have today?"
  • "Help me check whether there are any meetings this Wednesday afternoon"
  • "What is tomorrow's schedule?"
  • "Check whether there are any recent schedules about project review"
  • "What schedules do I have from next Monday to Friday?"

Process:

  1. Calculate the time range based on user intent (e.g., "today" → same day 00:00:00 to 23:59:59, "this week" → Monday to Sunday of this week)
  2. Call get_schedule_list_by_range to get the schedule ID list
  3. Call get_schedule_detail to batch retrieve details and convert Unix timestamps to readable time
  4. If the user mentions a keyword (e.g., "project review"), match and filter in summary ; if not found, gradually expand the range up to a limit of 30 days before and after
  5. When displaying the schedule list, include key information such as title, time, location, and participants, so the user can quickly understand it

Create Schedule

Classic query examples:

  • "Help me create a meeting tomorrow from 2 PM to 3 PM, titled Requirements Review"
  • "Schedule a full-day team building activity on Friday"
  • "Create a schedule: the day after tomorrow at 10 AM, hold a product plan discussion meeting with Zhang San and Li Si, location is the 3rd-floor meeting room"
  • "Help me create a schedule, next Monday 14:00-15:00, remind me 15 minutes in advance"
  • "Set up a schedule for tomorrow morning, invite Wang Wei to attend"

Process:

  1. Parse the user intent and extract information such as time, title, location, participants, and reminder settings
  2. If participants are involved, first query the userid through wecom-contact-lookup ; if there are people with the same name, display the candidates for the user to choose
  3. If the user does not specify a reminder, set a reminder 15 minutes in advance by default (remind_before_event_secs: 900)
  4. If the user says "all-day", set is_whole_day: 1, and set the time to 00:00:00 to 23:59:59 of that day
  5. After confirming the schedule information with the user (title, time, location, participants, etc.), call create_schedule

Modify Schedule

Classic query examples:

  • "Move tomorrow's requirements review to the day after tomorrow at 3 PM"
  • "Help me change the title of this afternoon's meeting to Technical Plan Review"
  • "Change the location of my 14:00 schedule today to online Tencent Meeting"
  • "Postpone Friday's team building activity by one hour"
  • "Help me add a description to tomorrow's weekly meeting: discuss Q2 planning"

Process:

  1. First locate the target schedule through the query workflow (match by keywords such as the time and title mentioned by the user)
  2. If multiple schedules match, display a candidate list for the user to confirm
  3. Confirm with the user the fields to be modified and the target values
  4. Call update_schedule, passing only the fields that need to be modified

Cancel Schedule

Classic query examples:

  • "Cancel tomorrow afternoon's requirements review"
  • "Help me delete Friday's team building schedule"
  • "I don't want to have the 15:00 meeting today anymore, help me cancel it"

Process:

  1. First locate the target schedule through the query workflow
  2. Confirm with the user the schedule information to be canceled (title, time, etc.) to avoid accidental operations
  3. After confirmation, call cancel_schedule

Manage Participants

Classic query examples:

  • "Add Zhang San to tomorrow's requirements review meeting"
  • "Help me remove Li Si from Friday's schedule"
  • "Invite Wang Wei and Zhao Min again to tomorrow afternoon's meeting"
  • "Remove Liu Qiang from the participants of my technical sharing the day after tomorrow"

Process:

  1. Through wecom-contact-lookup get the target person's userid; if there are people with the same name, display the candidates for the user to choose
  2. Locate the target schedule by querying the workflow
  3. Call add_schedule_attendees or del_schedule_attendees to complete adding/removing

Query availability and schedule a meeting

Classic query examples:

  • "Help me check whether Zhang San and Li Si are free tomorrow afternoon"
  • "Check my and Wang Wei's free time this week, I want to set up a meeting"
  • "I want to have a meeting with Xiaoming and Xiaohong from the product team, see when everyone is free"
  • "Find a time slot tomorrow afternoon when everyone is free and schedule a 1-hour meeting"

Process:

  1. Get the userids of the relevant people via wecom-contact-lookup to obtain the userids of the relevant people
  2. Call check_availablity to query each user's busy time slots within the specified time range
  3. Analyze all users' busy time slots, calculate the common free time slots and recommend them to the user
  4. After the user confirms the time slot, call create_schedule to create the meeting and automatically add the participants