Sasha MCP reference

listSuggestions

List suggestions

List improvement suggestions filed on this instance, newest first, with their FEEDBACK reference and disposition. Filter by disposition, kind or age; page with cursor. A member sees only suggestions filed by its own connection; staff and admins see every suggestion.

Arguments

ArgumentTypeRequiredDescription
dispositionenum (received, watch, in-progress, shipped-canary, shipped-fleet, already-covered, refuted, held)optionalOnly suggestions with this disposition
kindenum (feature, bug, friction, docs)optionalOnly suggestions of this kind
sinceDaysintegeroptionalHow many days back to look (default 90)
limitintegeroptionalAt most this many suggestions (default 20)
cursorstringoptionalnextCursor from the previous page

Scopes

None. Any authenticated connection can call it.

Annotations

  • Read only: yes
  • Destructive: no

When to use

Call listSuggestions when a person asks what has been reported to the Sasha team, or whether a problem was already reported. You do not need to know an id or a reference first.

It needs no scope. Any authenticated connection can call it.

  • A member sees only the suggestions filed by its own connection. Staff and admins see every suggestion on this instance.
  • The list is newest first.
  • disposition is optional: only suggestions with this disposition (received, watch, in-progress, shipped-canary, shipped-fleet, already-covered, refuted or held).
  • kind is optional: feature, bug, friction or docs.
  • sinceDays is optional, 1 to 365. The default is 90 days.
  • limit is optional, 1 to 50. The default is 20.
  • cursor is optional. Pass the nextCursor of the previous page to get the next one. nextCursor is null on the last page.
  • Each suggestion has its ref (for example FEEDBACK-012), the reference to give a person. The numbers count every suggestion filed on this instance, so they are not continuous in a member's own list. ref is null for a suggestion filed while an older version of the instance was running, until the instance next starts. The text of detail, and who filed it, stay on the instance.

Example

{
  "disposition": "held",
  "limit": 2
}
{
  "suggestions": [
    {
      "id": "sug_4f1c9a2e7b3d5a6c8e0f1b2d",
      "ref": "FEEDBACK-012",
      "kind": "feature",
      "severity": "minor",
      "summary": "searchKnowledge should return every matching line in a file, not only the first",
      "disposition": "held",
      "dispositionNote": "Needs an owner decision on the result size.",
      "pr": null,
      "liveVersion": null,
      "createdAt": "2026-10-12T09:14:03.000Z",
      "updatedAt": "2026-10-13T05:40:11.000Z"
    }
  ],
  "nextCursor": null
}

Refusals and what to do

  • A disposition or kind outside the lists, a sinceDays outside 1 to 365, or a limit outside 1 to 50 is refused as invalid arguments. Correct the value and call again.
  • Error in listSuggestions: cursor is malformed: the cursor did not come from nextCursor. Start again without a cursor.

Related

  • suggestImprovement files a suggestion and returns its id and ref.
  • checkSuggestion reads one suggestion by its id or its ref.
  • getDocs has an improvements section that lists the last 30 days.
made with bernard

Cookie settings