API скрейпера Google

Use the Lovely Router Google data tools to get data for me. They return JSON and are billed per result.

- Docs (read first): https://lovelyrouter.com/docs/tools.md and https://lovelyrouter.com/docs/tools/run.md and https://lovelyrouter.com/docs/api/tools.md
- Tools for this:
  - `google-search`: Поиск в Google ($0.00125 / page)
  - `google-news`: Поиск в Google News ($0.006 / article)
  - `google-play-reviews`: Отзывы Google Play ($0.000195 / review)
  - `google-trends`: Интерес в Google Trends ($0.039 / call)
  - `google-ads-transparency`: Google Ads Transparency ($0.0024 / ad)
  - `google-flights`: Поиск в Google Flights ($0.01125 / call)
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Each tool takes its own input fields: read them with GET https://lovelyrouter.com/v1/tools/<id> (public, no key needed) before the first run.
- If you support MCP, you can instead connect the server https://lovelyrouter.com/mcp (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.

My task: <describe the data you need and the output format>