campaignstack_submit_feedback
Submit a feedback report or bug report to the CampaignStack team. Call this when the user asks to report a bug, request a feature, or send feedback from this conversation. Mirrors the in-app feedback widget: same store, same email notification. Categories: 'bug', 'feature', 'question', 'other'. It does not open a support ticket or get a reply back through this connection.
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": {
"category": "<category>",
"message": "<message>",
"route": "<route>"
},
"name": "campaignstack_submit_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| route | Yes | The app route or context where the feedback originates (e.g. '/dashboard/campaigns' or 'mcp-agent') | |
| message | Yes | The feedback body text | |
| category | Yes | Feedback category: bug (something broken), feature (new capability request), question (how-to), other | |
| workspaceId | No | Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reportId | No | ||
| submitted | No |