Send feedback to the NexLev team without leaving the chat. Report something broken, suggest how a tool could work better, or ask for a feature that doesn't exist yet.
Feedback can come from you or from your AI assistant. Ask the assistant to pass along what you said, or let it file a report itself when a NexLev tool returns wrong, confusing, or missing data, or when none of its tools can do what you asked.
Prerequisites
- Connected AI assistant: Claude, ChatGPT, or any MCP-compatible client. See the Quickstart.
- Signed in to your NexLev account: anonymous connections cannot send feedback.
- Any plan, including Free.
Tool
nexlev_feedback_for_agents_humans
Sends one piece of feedback to the NexLev team: a bug, an improvement, a feature request, or anything else.
Best for:
- "This tool gave me numbers that don't add up"
- "I wish this tool could also…"
- "Nothing in NexLev does X. Please add it"
- Your assistant reporting a tool that returned an error or empty results it shouldn't have
Example prompts:
Tell NexLev that similar-channel search ignored my Shorts filter. I asked for Shorts-only channels like @channelhandle and got long-form channels back.
Write up the problem we just hit as a bug report: the tool, the exact arguments you used, what we expected, and what came back. Show me the draft before you send it.
File a feature request: I want frame extraction to accept a video's chapter list instead of timestamps I have to type. Explain that I study one frame per chapter to map how a video is structured, so it would save a step on every video.
For the rest of this chat, if any NexLev tool gives you an error, empty results, or data that contradicts another tool, tell me and offer to file a bug report. Don't send anything without my OK.
I've mentioned three things today: the Shorts filter issue, wanting batch metrics for more than 10 channels, and wanting results as a spreadsheet. Combine them into one clear feedback note so it only uses one of my monthly submissions.
Parameters:
| Parameter | Required | Description |
|---|---|---|
category | Yes | bug (broken or wrong), improvement (an existing tool could be better), feature_request (something new), or other |
title | Yes | A short summary, 3–150 characters |
message | Yes | The full note, 10–4,000 characters. For a bug: which tool, what you asked, what you expected, and what happened |
submitted_by | No | human if it is your words, agent if the assistant wrote it. Defaults to agent |
related_tool | No | The NexLev tool it is about, for example search_videos |
Example call:
{
"category": "bug",
"title": "search_videos returns no outliers for a channel that has them",
"message": "Asked search_videos for outlier videos from channel UC_EXAMPLE. Expected the channel's 3 known outlier videos, which the NexLev dashboard shows. Got an empty list.",
"submitted_by": "agent",
"related_tool": "search_videos"
}Write Feedback That Gets Acted On
Be specific. A report the team can reproduce is far more useful than a complaint.
| Weak | Strong |
|---|---|
| "It doesn't work." | "search_videos returned no outliers for a channel that has them in the dashboard." |
| "Search is bad." | "Similar-channel search ignored my Shorts filter and returned long-form channels." |
| "Add more stuff." | "Let frame extraction take a chapter list, so I can grab one frame per chapter without typing timestamps." |
For a bug, include:
- The tool: put it in
related_tooltoo - What you asked: the prompt or the arguments
- What you expected
- What actually happened: the error text or the wrong result
For a feature request, say what you are trying to get done and why it matters, not just the feature. "I research 20 channels a week and compare them by hand" tells the team more than "add export".
Allowance
5 submissions per account per calendar month (UTC).
- The cap is per account, not per API key: every connection on your account shares the same 5.
- At 5, nothing else is saved until the month resets, and the reply tells you the reset date.
- Free on every signed-in plan, including Free.
- Does not count against your weekly MCP tool-call allowance.
- Never uses usage credits and never bills.
| Plan | Feedback per month |
|---|---|
| Free | 5 |
| Lite / Premium / Niche Finder | 5 |
| Pro / N8N Pro | 5 |
FAQ
Can my AI assistant send feedback without me asking?
Yes. The tool is built for both people and agents. When a NexLev tool returns wrong, confusing, or missing data, or when nothing it has can do what you asked, your assistant can file a report on its own and marks it submitted_by: agent. If you'd rather approve every report, tell it to ask first.
Can I see or edit feedback I already sent?
No. Feedback is submit-only. It cannot be listed, edited, or deleted from the assistant afterwards.
Does sending feedback use my tool-call allowance or credits?
No. Feedback has its own limit of 5 per month and does not touch your weekly MCP tool-call allowance or your usage credits.
What happens when I hit 5 in a month?
Further submissions are not saved until the next calendar month (UTC). The reply tells you the reset date.
Is this the right place for account or billing problems?
For anything you need a direct answer on, like access, plan, or billing, email contact@nexlev.io or check Troubleshooting. Use this tool for product feedback: bugs, improvements, and ideas.
What's Next?
- Quickstart: Connect NexLev to your AI assistant
- Video Frame Extraction: Study editing, animation, and camera style frame by frame
- MCP Troubleshooting: Fixes for common connection and quota issues