feedback
End-user app feedback sent to the project's private owner inbox (destination: "project_owner_inbox") — this does not reach the Somewhere platform team. Every successful submission repeats that destination and names the exact platform-support calls. Submit: provide a message about that project's own UI or behavior. List: without message it returns feedback on a project you own. When the project owner resolves one of these reports, the owner-facing project channel can emit a feedback_resolved event.
Platform bugs, missing capabilities, deploy/API problems and documentation issues are out of scope for this tool. support_ticket({ message: "..." }) sends such a report to the platform support queue.
Example:
// Submit:
{ "project_id": "my-saas", "message": "The checkout button in this app does nothing after I enter my card" }
// List:
{ "project_id": "my-saas" }Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>"
},
"name": "feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | Feedback message. Omitted: feedback is listed instead. | |
| page_url | No | Optional page URL the feedback is about (submit mode) | |
| project_id | Yes | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |