RIrillet
Feedback

Reports API or MCP bugs and missing features

Changed on

Found something surprising, confusing, or missing while using the API or MCP tools? Tell us, even if you found a workaround. Report unclear tool schemas, confusing results, missing filters, excessive pagination, or missing bulk operations. Send one observation per request. Describe what you were trying to do and what you expected; for bugs, also include what actually happened. For MCP feedback, set endpoint to /mcp and include the affected tool name in description, for example list_all_journal_entries. You do not need to know the tool's underlying REST path. For API feedback, set endpoint to the affected API path. A writable API key or OAuth token with write scope is required. The organization and submitting credential are recorded from authentication, so you do not need to provide them.

post/feedback

Request

Request body

kind'BUG' | 'MISSING_FEATURE' required

Use BUG for unexpected behavior or MISSING_FEATURE for a capability you need.

titlestring required

A short summary of the issue or request.

endpointstring required

The affected API path, starting with /. For MCP feedback, use /mcp and name the affected tool in description. For a missing API endpoint, use the closest related path.

agentNamestring

Optional name of the agent or integration that encountered this issue.

descriptionstring required

What you were trying to do and why the issue matters. For MCP feedback, include the affected tool name. Include sanitized request details if useful.

actualBehaviorstring

Required for BUG. Describe what happened, including a sanitized tool error or API status code if available.

expectedBehaviorstring required

What you expected instead, or the capability that would let you complete the task.

Example request

{
  "endpoint": "/invoices"
}

Response

Feedback recorded

idstring uuid required

Changes