find_meeting_time
Find ranked meeting time suggestions across structured locations, with an optional ISO or natural-language date resolved by the first location's timezone.
Instructions
Return ranked meeting suggestions from the production meeting search endpoint. Use when you have structured locations and, optionally, a date. date may be ISO YYYY-MM-DD or a simple human day/date value such as "Thursday", "tomorrow", or "next Friday"; findtime.io resolves it relative to the first location timezone. Paste shareText to the user. plannerUrl carries aiCities, up to three UTC aiSlots, legacy aiTime, and ref=mcp-bot. Do not invent wall-clock times. Route vague or mixed-intent raw prompts to answer_time_question.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "find_meeting_time"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Optional date to anchor the meeting search. Prefer ISO YYYY-MM-DD, but simple human values such as "Thursday", "tomorrow", or "next Friday" are accepted. | |
| locations | No | ||
| _endUserId | No | Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Use a non-PII hash or token; never send raw email, name, or platform user ID. | |
| countryCodes | No | ||
| durationMinutes | No | Optional meeting length. Only 30, 45, or 60 are written onto the planner link as aiDuration. |