submit_feedback
Report errors, request missing features, and share quality signals about Commune's API directly to the product team.
Instructions
Submit feedback about Commune to the product team.
Use this tool whenever you encounter something worth reporting — an error, a missing capability, or an observation about what's working well or could be improved.
Three feedback types:
"error" — the API returned a non-2xx status, the response shape was wrong, or behavior was incorrect (not just unexpected). Include context: which tool you called, what you expected, what happened. Example: "list_threads returns 500 when the inbox has never received a message."
"feature" — you need a capability that doesn't exist yet. Be specific about the use case. Example: "Need cursor-based pagination on search_threads — current limit cap blocks processing large backlogs."
"signal" — the API succeeded but quality, latency, or behavior was unexpected. Also use for positive observations. Example: "Semantic search quality on long threads is excellent — intent matching across 40+ messages works." Example: "Thread metadata endpoint is slow (~3s) on inboxes with 1000+ threads — expected <500ms."
The optional context dict lets you attach structured metadata that makes feedback actionable. For errors, include the tool name, any IDs, and status codes. For features, include the related tool and your use case.
Args: type: Feedback type — "error", "feature", or "signal" message: Clear description of the feedback (max 4000 chars) context: Optional structured metadata, e.g. {"tool": "list_threads", "inbox_id": "inb_123", "status_code": 500}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | ||
| context | No | ||
| message | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |