Skip to main content
Glama
flowsery

flowsery

Official

List Detected Issues

list_issues
Read-onlyIdempotent

Lists bugs, broken flows, and UX problems the AI found in session recordings, deduplicated and ranked by severity or recency. Start here to see what is broken on a site, then drill into one issue.

Instructions

List issues the AI found while analyzing session recordings: bugs, broken flows, and UX problems, deduplicated across sessions and ranked by severity (or by last seen with sort recency). Each row has title, severity, status, sessions affected, and first/last seen; the response also carries site-wide open, in_progress, and resolved counts plus pagination.total. Start here for 'what is broken', then call get_issue with an id for occurrences, steps to replicate, and comments. Suspended issues are hidden unless status is suspended, so an issue that vanished was probably suspended, not deleted. On a free trial only the first 10 issues are listed and counted. Requires websiteId or domain with a workspace token.

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_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoseverity puts the most severe issues first; recency puts the most recently seen first. Omit to sort by severity.
limitNoPage size: how many issues to return in this call. Omit for 100.
domainNoWebsite domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
offsetNoHow many issues to skip, for reading the next page. Omit to start at the first one.
searchNoWords to look for in issue titles and descriptions, e.g. "checkout"
statusNoOnly list issues in this workflow state: open is new and untriaged, in_progress is being worked on, resolved was marked fixed, suspended was hidden as a known non-problem. Omit to list open, in_progress and resolved together; suspended issues appear only with status suspended.
severityNoOnly list issues at this severity, as rated by the AI that found them. Omit to include every severity.
websiteIdNoWebsite ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key.
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv1.5.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / limit / description
      Previous value: -"Max issues to return (1-1000, default 100)"New value: +"Page size: how many issues to return in this call. Omit for 100."
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / offset / description
      Previous value: -"Issues to skip for pagination (default 0)"New value: +"How many issues to skip, for reading the next page. Omit to start at the first one."
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / search / description
      Previous value: -"Match against issue title and description"New value: +"Words to look for in issue titles and descriptions, e.g. \"checkout\""
    • changedInput schema / properties / severity / description
      Previous value: -"Filter by severity"New value: +"Only list issues at this severity, as rated by the AI that found them. Omit to include every severity."
    • changedInput schema / properties / sort / description
      Previous value: -"Order by severity (default) or recency (last seen)"New value: +"severity puts the most severe issues first; recency puts the most recently seen first. Omit to sort by severity."
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status. Omit for open, in_progress, and resolved together; suspended issues only appear with status=suspended"New value: +"Only list issues in this workflow state: open is new and untriaged, in_progress is being worked on, resolved was marked fixed, suspended was hidden as a known non-problem. Omit to list open, in_progress and resolved together; suspended issues appear only with status suspended."
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
      +  "type": "string"
      +}
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedOutput schema / properties / result / additionalProperties
      Added value: +true
    • removedOutput schema / properties / result / description
      Removed value: -"Object with status, data (issues with id, title, severity, status, sessionsAffected, firstSeenAt, lastSeenAt), counts {open, inProgress, resolved} for the whole site, and pagination {limit, offset, total}."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "counts": {
      +    "additionalProperties": true,
      +    "description": "Issue counts by status for the whole website, ignoring filters",
      +    "properties": {
      +      "inProgress": {
      +        "$ref": "#/properties/result/properties/counts/properties/open"
      +      },
      +      "open": {
      +        "$ref": "#/properties/result/properties/data/items/properties/sessionsCount"
      +      },
      +      "resolved": {
      +        "$ref": "#/properties/result/properties/counts/properties/open"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "data": {
      +    "items": {
      +      "additionalProperties": true,
      +      "properties": {
      +        "description": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "externalTicketKey": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "externalTicketProvider": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "externalTicketUrl": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "firstSeenAt": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "id": {
      +          "description": "Pass as issueId to get_issue or update_issue_status",
      +          "type": "string"
      +        },
      +        "lastSeenAt": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "sampleRecordingId": {
      +          "$ref": "#/properties/result/properties/data/items/properties/description"
      +        },
      +        "sessionsCount": {
      +          "description": "Analyzed sessions that hit this issue",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "severity": {
      +          "description": "low, medium, high or critical",
      +          "type": "string"
      +        },
      +        "status": {
      +          "description": "open, in_progress, resolved or suspended",
      +          "type": "string"
      +        },
      +        "stepsToReplicate": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "title": {
      +          "type": "string"
      +        },
      +        "websiteId": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "websiteId",
      +        "title",
      +        "severity",
      +        "status"
      +      ],
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "pagination": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "limit": {
      +        "type": "number"
      +      },
      +      "offset": {
      +        "type": "number"
      +      },
      +      "total": {
      +        "description": "Rows matching the query before paging",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "limit",
      +      "offset",
      +      "total"
      +    ],
      +    "type": "object"
      +  },
      +  "status": {
      +    "description": "\"success\" on every successful call",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "status",
      +  "data",
      +  "counts",
      +  "pagination"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / domain / description
      Previous value: -"Website domain to query. Required when using a workspace token unless websiteId is provided."New value: +"Website domain from list_websites (e.g. \"example.com\"). Alternative to websiteId with a workspace token."
    • changedInput schema / properties / limit / description
      Previous value: -"Max results"New value: +"Max issues to return (1-1000, default 100)"
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset"New value: +"Issues to skip for pagination (default 0)"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status. Default excludes suspended issues"New value: +"Filter by status. Omit for open, in_progress, and resolved together; suspended issues only appear with status=suspended"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Website ID to query. Required when using a workspace token unless domain is provided."New value: +"Website ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key."
    • changedOutput schema / properties / result / description
      Previous value: -"Issues with severity, status, sessions affected, first/last seen, plus open/in-progress/resolved counts and pagination."New value: +"Object with status, data (issues with id, title, severity, status, sessionsAffected, firstSeenAt, lastSeenAt), counts {open, inProgress, resolved} for the whole site, and pagination {limit, offset, total}."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds real behavior beyond them: deduplication across sessions, severity vs recency ranking, the aggregate open/in_progress/resolved counts, pagination.total, and a free-trial cap of 10 issues that truncates both the list and the counts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the primary next step, then progressively adds caveats (suspended visibility, trial cap, auth requirement). It is dense but nearly every clause carries actionable information; the return-field enumeration is mildly redundant given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, zero-required list tool with an output schema, the description covers what an agent needs: scope, ranking, hidden-state behavior, downstream call, auth prerequisites, and trial truncation. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by tying sort=recency to 'last seen' ordering and by explaining the suspended/status interaction that the schema only implies. Authentication semantics for websiteId vs domain with a workspace token are also restated usefully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list issues the AI found in session recordings) and enumerates the content types (bugs, broken flows, UX problems). It also distinguishes itself from the sibling get_issue by naming that tool as the drill-down step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to 'start here for what is broken, then call get_issue with an id', which gives both when-to-use and the follow-up routing. It also warns that suspended issues are hidden unless status=suspended, so an agent won't misread a missing issue as deleted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.