# Multi-city meeting planner

- Human page: https://happytails.ai/en/date-time-tools/multi-city-meeting-planner/
- Markdown: https://happytails.ai/en/date-time-tools/multi-city-meeting-planner.md
- Structured JSON: https://happytails.ai/agents/en/date-time-tools/multi-city-meeting-planner/index.json
- Visibility: public

## Tool capabilities

| Property | Value |
| --- | --- |
| Tool ID | `multi-city-meeting-planner` |
| Category | date-time-tools |
| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |
| Browser execution | Use the visible action or interactive controls. |
| Browser processing | Browser; see tool notes for network behavior. |
| HTTP API | Not callable through HTTP. |
| Browser-agent interface | run_current_tool |

### Implementation notes

Shared working hours are found on this device for 2 to 12 cities and up to 92 days, using the time zone rules built into your browser.

### Inputs and settings

Text input: Cities as CSV.

Example or placeholder shown in the interface (not a validated fixture):

```text
city,time_zone,start,end,days
```

Times are local 24-hour HH:MM. Days are MO to SU separated by spaces, or empty for Monday to Friday. Up to 5,000 characters. Review the settings before running.

| Setting | Meaning | Control type | Default | Constraints |
| --- | --- | --- | --- | --- |
| `from` | First date (empty for today) | date | "" |  |
| `to` | Last date (empty for two weeks) | date | "" |  |
| `referenceZone` | List the days in this time zone | text | "UTC" |  |

### Browser-agent workflow

1. Open the human page in a browser that supports WebMCP.
2. Discover the interface exposed by that page; use its actual schema.
3. Select files on the page first when the tool requires files.
4. Call `run_current_tool` with valid input and settings.
5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.

Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.

### Planning specification

2 to 12 cities, up to 5,000 characters and 92 days. Everything is calculated on your device in the background. Downloads: CSV, JSON report and an iCalendar (.ics) file.

This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.

### Complete machine-readable capability record

```json
{
  "id": "multi-city-meeting-planner",
  "category": "date-time-tools",
  "built": true,
  "requirements": "2 to 12 cities, up to 5,000 characters and 92 days. Everything is calculated on your device in the background. Downloads: CSV, JSON report and an iCalendar (.ics) file.",
  "implementation": {
    "fields": [
      {
        "key": "from",
        "label": "First date (empty for today)",
        "value": "",
        "type": "date"
      },
      {
        "key": "to",
        "label": "Last date (empty for two weeks)",
        "value": "",
        "type": "date"
      },
      {
        "key": "referenceZone",
        "label": "List the days in this time zone",
        "value": "UTC",
        "type": "text"
      }
    ],
    "registrationFamily": "travel-and-meeting-time",
    "inputMaxLength": 5000,
    "inputErrorCode": "TRAVEL_AND_MEETING_TIME_TOO_LONG_MEETING",
    "note": "Shared working hours are found on this device for 2 to 12 cities and up to 92 days, using the time zone rules built into your browser.",
    "experience": {
      "automatic": false,
      "single": false,
      "inputMaxLength": 5000,
      "inputMode": "text",
      "label": "Cities as CSV",
      "placeholder": "city,time_zone,start,end,days",
      "help": "Times are local 24-hour HH:MM. Days are MO to SU separated by spaces, or empty for Monday to Friday. Up to 5,000 characters. Review the settings before running.",
      "action": null
    },
    "mode": "explicit",
    "interactive": false
  },
  "execution": "Browser interface",
  "api": null,
  "browser_agent": {
    "supported": true,
    "name": "run_current_tool",
    "discovery": "WebMCP on the human page in a supporting browser",
    "verification": "See audit/API-AUDIT.md; availability is not verification"
  }
}
```

## Page guide

Find the hours when working days in several cities overlap. Each day lists the shared window in every city's local time and flags days near a clock change.

### How to use Multi-city meeting planner

1. Paste one row per city with its time zone, working hours and working days.
2. Choose the first and last date and the time zone used to list the days.
3. Review the shared windows and check any day flagged as near a clock change.
4. Download the CSV, the JSON report or a calendar file with each shared window.

How can we improve this tool?

Report a problem or share an idea.

Please leave out private information. Your message and the tool name go to our team via PostHog.

## Useful next steps

- [Time zone converter](https://happytails.ai/en/date-time-tools/time-zone-converter/) ([Markdown](https://happytails.ai/en/date-time-tools/time-zone-converter.md))

- [Meeting cost](https://happytails.ai/en/business-tools/meeting-cost/) ([Markdown](https://happytails.ai/en/business-tools/meeting-cost.md))

- [Date difference](https://happytails.ai/en/date-time-tools/date-difference/) ([Markdown](https://happytails.ai/en/date-time-tools/date-difference.md))

## How the overlap is found

For each day in the listing time zone, each city's working hours on its own local working days are converted to exact instants and intersected. Only time when every city is working counts. Working hours that end at or before they start run overnight.

### Clock changes

A day is flagged when any city, or the listing time zone, has a different UTC offset on the day before and the day after. Shared windows can move by an hour around these dates, so check them before you book.

### Limits

Time zone rules come from your browser and can differ slightly between browsers. Public holidays are not known; remove those dates yourself.