Submit Feedback to Sentry Team
submit_feedback_to_sentry_teamReport missing, broken, or confusing Sentry MCP tools and ideas to its maintainers, not your Sentry organization, so MCP friction is documented.
Instructions
Report friction with the Sentry MCP server to its maintainers (not the user's Sentry organization): a missing tool, a tool that failed or returned wrong data, a confusing tool, or an idea. Call it at most once per task, only when a Sentry MCP tool was missing, failed, or got in the way. Skip it if the task went fine or did not need Sentry; never use it to log progress or to test it. Do not include secrets or personal data.
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": {
"task": "<task>",
"kind": "<kind>",
"impact": "<impact>",
"description": "<description>"
},
"name": "submit_feedback_to_sentry_team"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | missing: no tool could do it; broken: a tool failed or returned something wrong; confusing: a tool or its docs were unclear; idea: a suggestion. | |
| task | Yes | A short phrase naming what the user asked you to do. | |
| impact | Yes | blocked: you could not finish; worked_around: you finished another way; friction: you finished, but it was harder than it should be. | |
| toolName | No | The Sentry MCP tool the feedback is about, if any. | |
| description | Yes | What you tried, including tool calls and any error, and what went wrong. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| feedbackId | Yes | ID of the feedback sent to the Sentry MCP maintainers. |