Feedback and reviews
Request features, report issues with the failing request attached, upvote, comment and review, from the board, MCP, the CLI or REST.
Glossa is built from what its customers ask for. The feedback board holds feature requests (public, so the same request gathers votes instead of being filed twice) and issue reports (private to your workspace and the Glossa team). Everyone who files, upvotes or comments on an item gets an email when it moves, through to done. Reviews are public, one per workspace.
Everything the board can do, your agent can do over MCP, the CLI and REST:
| Action | MCP tool | CLI (npx @meterapp/glossa …) | REST |
|---|---|---|---|
| List or search the board | list_feedback | feedback list | GET /api/v1/feedback (public) |
| One item, comments and timeline | get_feedback | feedback show <id> | GET /api/v1/feedback/{id} |
| My items and subscriptions | list_my_feedback | feedback mine | GET /api/v1/feedback?mine=true |
| Request a feature | request_feature | feedback request "<title>" | POST /api/v1/feedback/features |
| Report an issue | report_issue | feedback report "<title>" [--request-id] [--last] | POST /api/v1/feedback/issues |
| Upvote / remove | upvote_feedback / remove_feedback_vote | feedback upvote <id> [--remove] | POST / DELETE /api/v1/feedback/{id}/votes |
| Comment | comment_on_feedback | feedback comment <id> "<text>" | POST /api/v1/feedback/{id}/comments |
| Emails on or off | set_feedback_subscription | set_feedback_subscription --subscribed false | POST /api/v1/set_feedback_subscription |
| Post or edit a review | submit_review | review --rating 5 --body … | PUT /api/v1/reviews/me |
| Read reviews | list_reviews | reviews | GET /api/v1/reviews (public) |
Duplicates
request_feature and report_issue look for the same thing first. An identical active item gets your vote instead (no new item, and you are told so). When likely matches exist nothing is filed: the answer has filed: false and similar. Upvote the match and add your use case as a comment, or call again with force: true if yours is different. A vote on a duplicate goes to the original.
Issue reports and context
Attach what failed so it can be reproduced: the request_id from the error (every response carries X-Request-Id, every problem body a request_id, every MCP tool error ends with one) and context: op, project, key, locale, file, status, error_code, error, client. Projects, files and keys must be your workspace's. Context is capped at 128 KB and only you and the team ever see it. The CLI remembers the last failed call, so --last attaches it.
# The last call failed? File it with its request id and error attached.npx @meterapp/glossa feedback report "push_file drops plural forms in .stringsdict" --last --project ios-app
# Or over RESTcurl -X POST https://getglossa.dev/api/v1/feedback/issues \ -H "Authorization: Bearer $GLOSSA_API_KEY" -H "Content-Type: application/json" \ -d '{"title": "push_file drops plural forms", "request_id": "req_8f2c1a", "context": {"op": "push_file", "project": "ios-app", "file": "ios/Localizable.stringsdict"}}'Issues stay private. When others are likely to hit the same thing the team may publish it under a sanitized title, so they can upvote it without seeing your details.
Status and email
Items move open → planned → in_progress → done, or end as declined or duplicate. Every change is on the item's timeline with the team's note, and is emailed:
| You file a feature request | Thanks for the idea, with a link to it. |
| You report an issue | We got your report (ref #n), with the context we captured. |
| You upvote | Thanks for voting (at most one a day; later votes are folded into the next one). |
| Someone comments on what you filed | A digest of new comments, at most one a day. |
| The team replies | The official response, to everyone following the item. |
| Status changes | Planned, in progress, done (with what changed), declined (with why) or merged into another item. |
| You post a review / the team replies | Thanks for reviewing; we replied to your review. |
Feedback email is its own category: every one carries a one-click unsubscribe for feedback only, and set_feedback_subscription (or the dashboard's Feedback page) turns it off for one item or all of them. Removing your vote stops emails about that item unless you filed or commented on it.
Reviews
One review per workspace: a 1–5 rating, a title, what works, what should be better and what you use Glossa for. Edit it once an hour; earlier versions are kept. It publishes right away unless an automated check (a new account with no paid usage, links, profanity) holds it for a quick look. The team replies under reviews and hides only spam and abuse, never a review for being negative. marketing_consent: true lets Meter quote yours.
Limits
- 10 new items and 50 comments per workspace a day; one review edit an hour.
- At most 20 feedback emails per address a day.
- Titles up to 140 characters, bodies and comments up to 5,000.