Skip to main content
Glama
Flowsery

flowsery

Official
by Flowsery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Detected Issues

list_issues
Read-only

Identify bugs, broken flows, and UX problems from AI analysis of session recordings. Get deduplicated issues ranked by severity, with status, affected sessions, and site-wide counts.

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. Limit defaults to 100 (max 1000). Requires websiteId or domain with a workspace token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrder by severity (default) or recency (last seen)
limitNoMax issues to return (1-1000, default 100)
domainNoWebsite domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
offsetNoIssues to skip for pagination (default 0)
searchNoMatch against issue title and description
statusNoFilter by status. Omit for open, in_progress, and resolved together; suspended issues only appear with status=suspended
severityNoFilter by severity
websiteIdNoWebsite ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoObject 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}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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}."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds substantial behavioral context beyond this, including pagination behavior, default limits, the hiding of suspended issues unless explicitly filtered, and authentication requirements. It does not explicitly state it is read-only, but the annotations cover that, and the added context exceeds the minimal bar.

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

Conciseness5/5

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

The description is comprehensive yet tightly organized, flowing from what the tool does, to what it returns, to usage guidance, to special cases and requirements. Every sentence conveys necessary information without redundancy, making it efficient and easy to scan for an agent.

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?

It describes the output shape (rows with title, severity, status, sessions affected, first/last seen, plus aggregate counts and pagination.total) and explains when to use this tool vs. get_issue, covering the essential context an agent needs to invoke it correctly. The authentication requirement and suspended-issue behavior are also included, making it fully self-sufficient.

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

Parameters5/5

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

The schema already covers 100% of parameters with descriptions. The tool description supplements this by clarifying the relationship between websiteId and domain ('Requires websiteId or domain with a workspace token') and reiterating the limit default, adding meaning beyond what the schema alone provides for the critical authentication parameter.

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?

The description clearly states the tool lists issues found by AI analysis, enumerates the types (bugs, broken flows, UX problems), and distinguishes it from get_issue which retrieves details by ID. The intended resource (issue list) and action (list) are explicit, leaving no ambiguity about what this tool does.

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?

It provides explicit guidance on when to use this tool ('Start here for what is broken') and when to follow up with get_issue, while also noting the requirement for websiteId or domain with a workspace token. It explains the special handling of suspended issues and default limit behavior, giving clear direction on prerequisites and context.

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

Deploy Server

Other Tools