Skip to main content
Glama

Flowsery

by com.flowsery
OverviewDiscussionsAdmin

List Detected Issues

list_issues
Read-only

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. 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.
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

TableJSON Schema
NameRequiredDescriptionDefault
resultNoObject with status, data (issues with id, title, description, severity, status, sessionsCount, firstSeenAt, lastSeenAt, stepsToReplicate, externalTicketUrl), counts {open, inProgress, resolved} for the whole site, and pagination {limit, offset, total}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changed
    • changedOutput schema / properties / result / description
      Previous 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}."New value: +"Object with status, data (issues with id, title, description, severity, status, sessionsCount, firstSeenAt, lastSeenAt, stepsToReplicate, externalTicketUrl), counts {open, inProgress, resolved} for the whole site, and pagination {limit, offset, total}."
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed6 schema fields changed
    • 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}."
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds substantial context beyond them: deduplication across sessions, default severity ranking, suspended issues being hidden rather than deleted, a free-trial cap of 10 issues, and the auth requirement (websiteId or domain with a workspace token). This is exactly the behavioral detail annotations cannot convey.

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 the core purpose and routing to get_issue before the finer details of counts, trial limits, and pagination. Dense but nearly every clause carries actionable information; slightly long with some redundancy between the response-field listing and the existing output schema.

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?

Covers what the tool returns (row fields, site-wide counts, pagination.total), how records can disappear, trial limitations, and default/max limits. Even though an output schema exists, the added context about suspended issues and trial truncation makes the description fully sufficient for correct invocation.

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 already 100%, so the baseline is 3, but the description reinforces key semantics: limit defaults to 100 with a 1000 max, recency means 'last seen', and status omission covers open/in_progress/resolved while suspended is opt-in. It doesn't add format or syntax beyond the schema, so not a 5.

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 while analyzing session recordings') and immediately enumerates the resource's content (bugs, broken flows, UX problems) with dedup and severity ranking. It is clearly distinguishable from siblings like list_websites and get_issue.

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 positions itself as the entry point ('Start here for what is broken') and names the follow-up tool with its purpose ('then call get_issue with an id for occurrences, steps to replicate, and comments'). It also explains the suspended-status edge case so an agent can interpret a missing issue correctly.

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

All Flowsery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources