Mine YouTube comments for product feedback and audience questions
Export comments from YouTube videos and Shorts as JSON with text, likes, replies count, author and date, to find feature requests, complaints and questions.
A review of your product, or of a rival's, can hold thousands of comments, and the useful ones are buried: the person who asks for a missing feature, the one who explains why they returned it. Scrolling through them does not scale. Lovely Router reads them for you. Send video links, get one JSON object per comment, pay per comment from a prepaid balance. Feed the result to a spreadsheet, a classifier or an AI agent with one API key.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Mine YouTube comments for product feedback and audience questions. Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- 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`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (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: <the inputs (links, keywords or accounts) and how many results you need>How it works
Pick the videos
Choose the review videos, tutorials, launch videos or competitor videos where your audience talks. Links to Shorts work too.
Run the tool with a cap
Send the links to
POST /v1/tools/youtube-comments/run, withsortset totoporlatest,maxItemsfor the number of comments andmax_resultsas the run cap. The run holds its maximum cost from your balance and returns the comments as JSON.Tag and count
Ask a model to label each comment (question, complaint, feature request, praise), then count by label and sort by likes to see what matters most.
Get the comments of a video with one request
List YouTube comments takes video or Shorts links in startUrls. Use sort: "top" for the comments people agree with, or "latest" for fresh reactions:
curl https://lovelyrouter.com/v1/tools/youtube-comments/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{
"input": {
"startUrls": ["https://www.youtube.com/watch?v=xObhZ0Ga7EQ"],
"sort": "top",
"maxItems": 20
},
"max_results": 20
}'A run still going after 60 seconds returns 202; Run a tool shows how to poll. One run can return up to 500 comments. Replies are not included; each comment carries its replies count.
What each comment holds
| Field group | What you get |
|---|---|
| Content | The comment text |
| Reach | Likes |
| Conversation | Number of replies |
| Author | The commenter's name |
| Timing | Comment date |
Recipes
Pull the top 300 comments of a rival's review video, ask a model to extract every request and complaint, and rank them by the likes on the comment.
Take the comments from your own tutorials, keep the ones with a question, and turn the most liked into FAQ entries or a follow-up video.
Run sort: "latest" on your launch video every few hours for a day and flag sentiment shifts or a bug that several people report.
Pull comments from review videos of both, and compare what the audience praises and what it complains about.
Look at the authors whose comments get the most likes and replies across several videos.
Prefer plain words? Connect the MCP server and tell Claude Code or Cursor: "Get the top 100 comments from this YouTube video, group them into questions, complaints and feature requests, and list the five most liked in each group. Set max_results to 100."
Pair it with other YouTube sources
Comments are the reaction. To place them in context:
Comments on YouTube videos or Shorts: text, likes, replies count, author, date. Sorted by top or latest.
YouTube videos for search keywords, or from YouTube links (search results, channel, playlist or video URLs): title, views, likes, comments count, duration, channel, date.
Videos from YouTube channels (handles such as @MrBeast, or channel URLs): title, views, likes, comments count, duration, date.
Full transcripts (captions) of YouTube videos, with timestamps: one per video link, in the language you ask for when the video has it.
A Reddit thread's post and comments by URL: text, score, author, date, reply depth.
youtube-searchfinds the review videos worth reading, by keyword.youtube-channellists a channel's videos with views, so you pick the ones with the most discussion.youtube-transcriptgives what the video said, to match comments to claims.reddit-commentsadds the same kind of feedback from a different crowd.
For the wider routine, see social listening.
What you pay
You pay per comment: starting a run holds its maximum cost, the per-call fee plus the per-comment fee times max_results, and the run settles to what it returned. The rest of the hold goes back to your balance. A run that fails or times out pays only for the comments it delivered, and a run refused at the start costs nothing.
Reading 500 comments is billed as 500 comments. There is no subscription and no monthly minimum: top up from $5, and one balance pays for tools and models. The card above shows today's price; pricing lists every tool.
Frequently asked questions
Can I get comments from Shorts?+
Yes. The tool takes YouTube video or Shorts links in startUrls.
Can I sort by newest or by most liked?+
Yes. sort accepts top or latest.
Are replies included?+
No. The tool returns top-level comments, and each one shows how many replies it has.
How many comments can I get?+
Set maxItems for the number per run. The run cap max_results goes up to 500 comments per run.
Do I need a YouTube account or API quota?+
No. You send links and an API key.
Do I need a subscription?+
No. You add credit to a prepaid balance and each run draws it down. Failed runs pay only for the results they delivered, and nothing renews automatically.
Comments are the voice of the customer. See review monitoring, social listening and the tool catalog.