Skip to main content
Glama
Flowsery

flowsery

Official
by Flowsery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Issue Detail

get_issue
Read-only

Retrieve complete evidence for an AI-detected issue: timestamps, sessions, steps to replicate, comments, and linked tickets. Use when you need the full context behind one issue.

Instructions

Get full detail for one AI-detected issue: every occurrence with timestamps, the sessions behind it, steps to replicate, comments, and any linked Linear or Jira ticket. Get issueId from list_issues; use this only when you need the evidence behind one issue. An unknown id, or one from another website, fails with 'Issue not found'; on a free trial, issues beyond the first 10 fail with 'Upgrade to view this issue'. Session detail names pages, referrers, and geography, so surface only what answers the question. Requires websiteId or domain with a workspace token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoWebsite domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
issueIdYesIssue ID from list_issues
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 and data: the issue with its occurrences, affected sessions, steps to replicate, comments, and external ticket link if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / 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: -"The issue with occurrences, affected sessions, steps to replicate, comments, and external ticket link if any."New value: +"Object with status and data: the issue with its occurrences, affected sessions, steps to replicate, comments, and external ticket link if any."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't repeat that. Instead it adds valuable behavioral details: exact error messages for unknown/trial cases, the fact that session detail includes pages/referrers/geography, and the note to surface only what answers the question. No contradiction with annotations.

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?

While the description is moderately long, every sentence earns its place. It front-loads the core purpose, then packs in retrieval source, usage scope, failure modes, and auth requirements without fluff. The structure is logical and scannable.

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?

Given the output schema exists (so return format is covered), the description still adds essential context: error handling, trial limits, the auth token requirement, and a tip on filtering session details. Nothing an agent needs to call this 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. The description adds useful context beyond the schema: where to get issueId, that websiteId/domain are alternatives, and that websiteId is ignored with a website key. This clarifies the auth model beyond the property descriptions, so a 4 is warranted.

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 ('Get') and resource ('one AI-detected issue'), and enumerates the exact details returned: occurrences, timestamps, sessions, steps, comments, and linked tickets. This clearly distinguishes it from list_issues (which lists issues) and update_issue_status (which mutates).

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 instructs to obtain issueId from list_issues and limits usage to 'only when you need the evidence behind one issue'. Also gives failure conditions for unknown IDs, cross-website IDs, and free-trial limits, plus the authentication requirement for websiteId/domain. This provides clear when-to-use and when-not-to-use guidance.

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