folders_create
ChatGPTCreate a new folder in a map to organize spots. Returns the folder with its ID, which you can use with spots_update or spots_update_bulk to assign spots.
folders_delete
ChatGPTDelete a folder from a map. Spots in the folder are unassigned but not deleted. Get folder IDs from maps_get.
images_upload_info
ChatGPTReturns how to upload a local image file directly (multipart POST) to attach to spots, for clients that can do real file uploads. Does not upload anything itself.
maps_create
ChatGPTCreate a new empty map. Returns the new map with its ID, which you can then pass to spots_create to add spots to it.
maps_get
ChatGPTGet full details for a specific map, including its folders and settings. Use this when you need more info than maps_list provides.
maps_list
ChatGPTList all the user's maps (owned and shared). A map is a collection of spots (points of interest). Call this first to get map IDs needed by other tools like spots_list, spots_create, or maps_get.
maps_show
ChatGPTShow a map to the user as a visual card: the map with its spots, the spot count and a button to open it in Ikuzo. Call this after you create a map or add, move or update spots, so the user sees the result, and whenever the user asks to see a map.
maps_update
ChatGPTUpdate a map's title or public sharing settings. Use this to rename a map or toggle public access on/off.
ping
ChatGPTTest connection and verify your API key is valid.
places_search
ChatGPTSearch Google Places to find real locations with accurate GPS coordinates and Place IDs. Always search first before creating a spot — use the returned placeId and gps with spots_create for verified, accurate locations. Counts against search quota (not MCP quota).
quota
ChatGPTCheck how many MCP calls you have left. Returns used/remaining calls and reset date. This call itself does not count against the quota.
routes_create
ChatGPTCreate a route on a map through some of its spots, in travel order. Computed along real roads (driving), paths (walking) or bike routes (cycling), or straight segments; a leg with no road (a ferry, say) is drawn straight. A public route can appear on the images of the map that websites embed. Each route counts against the monthly route quota of the account.
routes_delete
ChatGPTDelete a route (soft delete).
routes_list
ChatGPTList the routes of a map (lines drawn along roads, paths or straight). Returns routeId, name, profile, visibility, distance and duration.
schema
ChatGPTGet the valid values for spot types (categories like food, cafe, hotel...), statuses (visit states like visited, to visit...), and periods (seasons). You MUST call this before using spots_create or spots_update to know which values are accepted.
spots_add_image
ChatGPTAttach a photo to a spot from a public image URL. The server downloads the image, resizes it, stores it in Ikuzo's image storage (GCS + CDN), and adds it to the spot. Requires write access to the spot's map. For direct local-file uploads, POST multipart to /api/mcp/upload instead (call images_upload_info for details).
spots_box
ChatGPTSearch for spots within a rectangular geographic area across ALL the user's maps (owned + shared). Use this when you have bounding box coordinates, e.g. for a country, region, or visible map viewport. For searching around a single point/city, prefer spots_nearby instead.
spots_copy
ChatGPTCopy spots to a different map. Images are preserved, but folder assignments are skipped (folders are map-specific). Useful for duplicating spots across trips or templates.
spots_create
ChatGPTAdd a new spot (point of interest) to a map. A spot represents a place like a restaurant, hotel, landmark, etc. You MUST call "schema" first to get valid values for type, status, and period fields.
spots_create_bulk
ChatGPTCreate up to 10 spots in one call. Much faster than calling spots_create individually. Validates all spots first, then inserts them all at once. You MUST call "schema" first to get valid values for type, status, and period.
spots_delete
ChatGPTSoft-delete a spot. The spot is hidden but can be recovered later. The map owner and people who can edit the map can delete.
spots_get
ChatGPTGet all details for a single spot by its ID. Use this when you already have a spot ID and need its full data (description, coordinates, imageUrl, etc.).
spots_list
ChatGPTList and filter spots within a SINGLE specific map. Requires a mapId. Use this to browse, search, or filter spots that belong to a known map. This is NOT for geographic/location search — if the user asks for spots "near", "around", or "in" a place/city/area, use spots_nearby instead.
spots_nearby
ChatGPTSearch for spots near a place, city, address, or coordinates. Searches across ALL the user's maps at once (owned + shared). Use this when the user asks about spots "near", "around", "close to", or "in" a location. Results include a "distance" field in km and are sorted closest first. To search within a single map instead, use spots_list.
spots_update
ChatGPTModify an existing spot. Only include the fields you want to change — omitted fields stay unchanged. Call "schema" first to get valid values for type, status, and period.
spots_update_bulk
ChatGPTUpdate up to 20 spots with the same field values in one call. All specified fields are applied to every spot. Use this to batch-set status, type, folder, etc. Call "schema" first for valid values.
steps_add
ChatGPTAdd a step to a travel plan itinerary. A step is either a "spot" (a place to visit, referenced by its spotId) or a "day" divider (a label like "Day 1 - Tokyo" to organize the schedule). Steps are ordered by orderKey.
steps_delete
ChatGPTRemove a step from a travel plan. This only removes it from the itinerary — the underlying spot is not deleted.
steps_update
ChatGPTUpdate a step in a trip: reorder it (orderKey), rename a day divider, change how you reach a spot (mode), or set its schedule: a day divider takes startTime/endTime, a spot step takes stayMinutes, arriveBy, stayUntil, and for the leg that reaches it legMinutes or departAt/arriveAt (timetable). Pass null to clear a field. Check the result with travels_get (days[] and steps[].schedule).
travels_create
ChatGPTCreate a new empty trip. A trip mixes spots linked from the user's maps (trips_add_spots) and spots that only exist for this trip (trips_add_place), split into days with steps_add type "day". Deleting the trip later removes its own spots but never touches linked ones.
travels_delete
ChatGPTDelete a trip. Only the owner can delete. Removes its steps and the spots that only existed for this trip; spots linked from the user's maps stay in those maps.
travels_get
ChatGPTGet a trip with its days and steps in order. A day starts where the previous one ended, so the first stop of a day has a leg from the last stop of the previous day. When a day has a startTime, the schedule is computed: steps[].schedule (arrive, leave, wait, late, missed_train) and days[] (start, end, slack against endTime, drive/stay/wait minutes, sunrise/sunset when the trip has a startDate, warnings: LATE, MISSED, TIGHT (less than the trip safety margin before a fixed time), OVER_END, UNKNOWN_LEG, and NO_NIGHT when a day ends somewhere that is not a hotel or house while another day follows). Steps: Each step is either a day divider (e.g. "Day 1 - Tokyo") or a spot, with its day, its mode (how you reach it from the previous spot of that day) and a leg (mode, distance). spot.linked is true when the spot lives in one of the user's maps (editing it edits that map; spot.mapTitle says which); false means it only exists in this trip. Distances are as the crow flies unless withRoutes is true, which computes real driving/walking/cycling legs (slower, uses the route quota).
travels_list
ChatGPTList all travel plans (trip itineraries). A travel plan is an ordered list of spots and day dividers that form a trip schedule. Call this to get travel IDs needed by travels_get or steps_add.
travels_update
ChatGPTRename a trip, or set its default mode (used for every leg without its own mode).
trips_add_place
ChatGPTAdd a place that only exists for this trip (a hotel, a station, a restaurant you will not keep). It becomes a trip-only spot, removed with the trip. Use places_search first to get exact coordinates and the placeId.
trips_add_spots
ChatGPTLink existing spots from the user's maps into a trip, in this order (appended at the end, or right after afterStepId). The spots stay in their maps; editing them in the trip edits them there. Spots the user cannot see are returned in missing.