send_feedback
Send your user's feedback to the Autoview team: a feature request, a bug report, a question, or anything else. Works with no account and no token (as a guest), or with your user's token. Each message is saved for a person to review before it goes to the team; there is no set response time. With a token, the account is attached on our side from the token, so do not add it. Never put passwords, API keys or other secrets in message. If your user wants an answer, put a way to reach them in contact (for example an email address), or with a token set contact to true to use the address on the account. Show your user the message and get their go-ahead before sending. message is up to 4000 characters. Limit: 2 per hour for each account, or for each guest. Returns { received, id, status, guest, remaining_this_hour, note }; pass note to your user. A refusal returns { error, code, fix }: bad_kind, message_empty, message_too_long, contact_too_long, invalid_token, feedback_rate_limited (with retry_at), feedback_unavailable, feedback_store_failed. Do what fix says.
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>",
"message": "<message>"
},
"name": "send_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | feature_request, bug, question, or other | |
| token | No | your Autoview account token — an av_mcp_ personal access token, generate one at /account/tokens/ on the Autoview site. Omit this if your MCP client already sends it as an `Authorization: Bearer` header (Claude Code, Cursor, and most non-browser clients do this automatically once configured). Optional here: leave it out to send as a guest. | |
| contact | No | optional: how to reach your user if they want a reply (for example an email address, up to 254 characters), or true to use the address on the account (token only). Omit for no reply. | |
| message | Yes | your user's feedback in their own words, up to 4000 characters. For a bug, say what was sent, what happened and what was expected; a trace or canonical_id from events helps. |