Meeting room booking is possible, but room discovery is missing from CLI docs and command surface

[timzhong1024]

Summary

lark-cli appears to support booking a meeting room when creating a calendar event, but there is no clear CLI/documented way to discover available meeting rooms first.

What is confusing

From lark-cli calendar +create --help, the --attendee-ids flag explicitly says it supports:

• user IDs: ou_...
• chat IDs: oc_...
• room IDs: omm_...

This strongly suggests that room booking is supported by adding a room attendee when creating an event.

However, I could not find a clear way in the CLI to do the prerequisite step:

• list rooms
• search rooms
• get room IDs (omm_...)
• check which rooms are available for a time slot

Problem

The command surface exposes the final step (use a room ID), but not the discovery step needed to actually obtain a room ID.

So the capability is technically present, but practically incomplete for a normal user workflow.

Expected workflow

A user should be able to do something like:

lark-cli calendar rooms list
lark-cli calendar rooms search --query "A座"
lark-cli calendar rooms freebusy --start 2026-03-28T16:00:00+08:00 --end 2026-03-28T17:00:00+08:00
lark-cli calendar +create --summary "研讨会" --start ... --end ... --attendee-ids omm_xxx

Current gap

At least from the currently visible CLI docs/help/schema:

• calendar resources only expose calendars, events, event.attendees, freebusys
• there is no obvious rooms resource
• there is no obvious room-listing shortcut
• there is no documentation path that explains how to discover room IDs before using them in --attendee-ids

Why this matters

For room booking, discovery is part of the core workflow, not an optional extra. If users can only book a room when they already know an opaque omm_... ID, the feature is much less usable.

Suggestions

• Add room discovery commands to the CLI surface
  • list rooms
  • search rooms
  • get room details
  • query room availability / freebusy
• If room discovery already exists via a raw API path, document it clearly in the CLI docs
• In calendar +create --help, if room omm_... is mentioned, also point users to the command/doc that explains how to obtain room IDs

Real-world context

This came up while trying to create a calendar event and book a room in Feishu/Lark. The CLI clearly implied room booking support, but did not provide an obvious way to discover the rooms needed to use that support.

[liangshuo-1]

Thanks for the detailed write-up! We've noted this request and will evaluate it in our roadmap.