Submit feedback
feedback_submitProactively call this tool whenever a SalesTouch tool appears broken, behaves unexpectedly, returns a misleading error, or blocks the task, even if the user did not explicitly ask for a bug report. Include the exact tool name, safe reproduction details without secrets, the observed result or error, expected behavior, and impact. Use it also for feature requests or useful general feedback. Submit one ticket per distinct issue, avoid speculative or duplicate reports, and continue the original task after reporting.
When to use it
Proactively report a concrete SalesTouch bug whenever a tool appears broken, behaves unexpectedly, returns a misleading error, or blocks the task, even without an explicit user request. Also use it for feature requests or useful general feedback.
salestouch:useRequirements
Example
Submit this SalesTouch feature request: add a dry-run preview before starting a LinkedIn outreach workflow.
{
"type": "feature_request",
"message": "Add a dry-run preview before starting a LinkedIn outreach workflow so I can verify the selected leads and final copy."
}{
"content": [
{
"type": "text",
"text": "{\n \"data\": { ... },\n \"meta\": null\n}"
}
],
"isError": false
}Expected: A confirmation containing the new PostHog Conversations ticket id and creation time.
Parameters
typerequiredstringFeedback category: bug, feature_request, or general_feedback.
messagerequiredstringConcrete feedback with enough context for the SalesTouch product team.
Aliases are shown independently because MCP clients send a flat JSON object. Use one alias from each required group, not every alias.
Common errors
invalid_inputUse a supported type and provide a non-empty message within the published limit.
feedback_service_unavailableTry again after SalesTouch restores its PostHog Conversations configuration.
feedback_rate_limitedWait before submitting another feedback ticket.
feedback_submission_failedDo not retry automatically because the delivery result may be ambiguous.