Repository navigation
fix: feedback_tool sends feedback to the app's developer, not to Mapbox - #329
Merged
Merged
Conversation
The Feedback API is free during Public Preview, so drop the claims that a report may be billed or that a duplicate adds a charge. Say the report is filed under the user's own account, and add routing_issue to the categories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zmofei
reviewed
Nov 10, 2026
| name = 'feedback_tool'; | ||
| description = | ||
| 'Report a problem with Mapbox map, place or routing data to Mapbox through the Feedback API, ' + | ||
| 'Report a problem with Mapbox map, place or routing data through the Mapbox Feedback API (Public Preview), ' + |
Member
There was a problem hiding this comment.
feedback_tool is designed to let users of a Mapbox developer’s app report issues to that developer, rather than to Mapbox.
In a separate PR, we could extend the report tool to handle MCP or general Mapbox issues. Let’s clarify these use cases in the tool descriptions.
Per review: the Feedback API is how end users of a developer's app send feedback to that developer. Items land in the token owner's account and Feedback Explorer. Reword the description, confirmation, result and README around a developer building an app or agent on this server with their own token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mattpodwysocki
changed the title
1 of 2 tasks
Per review, like Feedback Agent: feedback can be about the app itself, not only map data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cription # Conflicts: # CHANGELOG.md
The Feedback API requires lat/lon, and the Feedback API team asked us to send 0, 0 for feedback without a place until location becomes optional. That feedback skips the duplicate check, since it would all match at 0, 0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zmofei
approved these changes
Nov 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
feedback_tooldescription didn't match what the Feedback API is for.The Feedback API is how end users of a developer's app send feedback to that developer. Items land in the token owner's account, in the same feed as Feedback Agent reports, and the developer reviews them in Feedback Explorer. They don't go to Mapbox. So the tool's real use case is a developer who builds an app or agent on this server with their own token: their users' feedback reaches them.
What was off
routing_issue, which wasn't in our category enum.Changes
routing_issue.No behavior change beyond accepting
routing_issue. Feedback about the MCP server itself goes throughreport_tool(#330).🤖 Generated with Claude Code