Send feedback
submit_feedbackReport a gap or problem in this Clerk MCP server so the Clerk team can fix it. Call it as soon as you find it, then continue the task: when none of these tools can do what the task needs (the most useful kind of report), when a tool error stops the task or a tool returns something wrong, when a tool or its documentation is confusing, or when the user asks you to report something. You do not need to ask the user first. Never include secrets, API keys, tokens, or personal data about end users.
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": {
"kind": "<kind>",
"task": "<task>",
"description": "<description>"
},
"name": "submit_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | What kind of problem: "missing" (no tool could do what the task needed), "broken" (a tool failed or returned something wrong), "confusing" (a tool or its documentation was unclear), or "idea" (a suggestion that would have helped). | |
| task | Yes | A short phrase naming what the user asked you to do, such as "Add an organization switcher". | |
| error | No | The exact error you received, with any secrets removed. | |
| impact | No | How the task went, if known: "blocked" (cannot finish), "worked_around" (finished another way), or "friction" (finished, but it was harder than it should be). Omit it when the task is still going. | |
| operation | No | Name of the tool the problem is about, such as create_user. Omit it when no tool was involved. | |
| suggestion | No | What would have helped. | |
| description | Yes | What you tried, including each tool call you made, and what went wrong or was confusing. Include both. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| received | Yes | ||
| feedback_id | Yes |