Send feedback to BankSync
send_feedbackSend product feedback to the BankSync team as the signed-in user: a bug report, a feature request, or general feedback. Use it when the user asks you to report a problem with BankSync or request something from it — not for questions you can answer, and never without the user asking. The team reads every submission and replies to the user by email when there is something to say; the reply is not returned here. Include the user's own description and the steps that led to a problem; never include passwords, API keys, or account numbers. Returns { submitted: true, submissionId } — the UUID that identifies this feedback; send it again as submissionId on a retry and it is recorded once.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
subject | string | required | A one-line summary, e.g. "CSV export drops the memo column". |
message | string | required | What happened or what is wanted, in the user’s words where possible: the steps, what they expected, and what they saw. Never include passwords, API keys, or account numbers. |
feedbackType | "bug" | "feature" | "general" | "other" | optional | bug, feature (a request), general (default), or other. |
area | "banks" | "integrations" | "enrichments" | "data_products" | "dashboards" | "billing" | "mcp" | "account" | "other" | optional | The part of BankSync it is about: banks, integrations, enrichments, data_products, dashboards, billing, mcp (default — this agent connection), account, or other. |
submissionId | string | optional | Optional. A UUID you generate once for this piece of feedback and send again on a retry, so a retried call records it once. Omit it and one is minted and returned: send that value back on a retry of the same feedback. |
Example call
The tool call an MCP client sends (required arguments shown with placeholder values).
{"tool": "send_feedback","arguments": {"subject": "value","message": "value"}}