fix: migrate to new Google Places API (New) to resolve HTTP 403 errors

[david-pivonka]

Google Places API Migration Fix

Problem

The get_place_details tool was returning HTTP 403 errors with the message:

Failed to get place details for ChIJQ2BmJhVwhlQRPkt6FWiet90: You're calling a legacy API, which is not enabled for your project. To get newer features and more functionality, switch to the Places API (New) or Routes API.

Solution

Migrated from the legacy Google Places API to the new Places API (New) to resolve the HTTP 403 errors and ensure continued functionality.

Changes Made

1. Added New Dependency

• Added @googlemaps/places package (v2.1.0) to package.json
• This is the official Google client library for the new Places API

2. Created New Service Class

• File: src/services/NewPlacesService.ts
• Implements the new Places API client
• Maintains backward compatibility by transforming the new API response format to match the legacy format
• Handles field mapping and data transformation

3. Updated PlacesSearcher

• File: src/services/PlacesSearcher.ts
• Modified getPlaceDetails() method to use the new NewPlacesService
• Maintains the same interface and response format for existing code

4. Key Features of the New Implementation

• Uses the new Places API (New) endpoint
• Proper field mask handling to avoid unnecessary billing
• Maintains backward compatibility with existing response structure
• Enhanced error handling for the new API
• Support for all existing place details fields (name, address, rating, reviews, etc.)

5. Testing

• Created test-new-api.js script to verify the new implementation
• Build process verified to work correctly
• Maintains existing functionality while using the new API

[cablate]

Thanks for the contribution!
The changes are quite extensive, so I’ll need a bit more time to review carefully.
I’ll get back to you as soon as possible.

[cablate]

LGTM.

I've improved New Place API work and remove obsolete Places API migration artifacts.