Support cases of your company, newest activity first (any member)
list_support_casesSupport cases of your company, newest activity first (any member).
scope=mine = cases the caller opened. state=open (default) = every status but closed; state=closed = closed cases. Internal notes are never counted or shown.
Check here before opening a case — the same problem may already be open (then reply there instead). Each item: id (case_…, what the other support tools take), number (e.g. CASE-1042, what people say), subject, category, severity, status, opened_by, last_activity_at, last_actor_kind. status: new (no answer from the team yet), waiting_staff (the team's turn), waiting_customer (the team answered and waits for your company), resolved (the team marked it fixed — it closes itself after 7 days without a reply), closed. state=closed lists closed cases; scope=mine only the token's user's. Paginated with cursor/next_cursor.
Support cases = asking the BoardMark team for help. Use them when the user wants help from the BoardMark team or reports a problem with BoardMark itself (a bug, signing in, billing, a feature request) — never for the user's own project work (that is issues: create_issue, search_issues …). Every member of the token's company sees and can answer every case of the company. The BoardMark team's replies arrive in the case thread (get_support_case), and followers also get them by email. Text only: files are attached in the web app (Help → Contact support). Your writes show as "via AI agent".
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_support_cases"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| scope | No | all | |
| state | No | open | |
| cursor | No | Opaque cursor from the previous page's `next_cursor`. |