Skip to main content
Glama
flowsery

flowsery

Official

Get Issue Detail

get_issue
Read-onlyIdempotent

Retrieve full evidence for one AI-detected site issue by ID: every occurrence with timestamps, affected sessions, reproduction steps, comments, and linked Linear or Jira tickets.

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 only the first 10 issues are available, and later ones fail as not included in the current plan. Each session lists its recording id, the anonymous visitorUid, start URL and page title, timing and event counts; no names, emails or locations are returned, so surface only what answers the question. Requires websiteId or domain with a workspace token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "issueId": "<issueId>"
    },
    "name": "get_issue"
  }
}

Input 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.
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. Changed9 schema fields changedv1.5.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • 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 and data: the issue with its occurrences, affected sessions, steps to replicate, comments, and external ticket link if any."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "data": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "comments": {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "authorName": {
      +              "$ref": "#/properties/result/properties/data/properties/description"
      +            },
      +            "body": {
      +              "$ref": "#/properties/result/properties/data/properties/description"
      +            },
      +            "createdAt": {
      +              "$ref": "#/properties/result/properties/data/properties/description"
      +            },
      +            "id": {
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "description": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "externalTicketKey": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "externalTicketProvider": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "externalTicketUrl": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "firstSeenAt": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "id": {
      +        "description": "Pass as issueId to get_issue or update_issue_status",
      +        "type": "string"
      +      },
      +      "lastSeenAt": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "occurrences": {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "atSeconds": {
      +              "$ref": "#/properties/result/properties/data/properties/sessionsCount"
      +            },
      +            "description": {
      +              "$ref": "#/properties/result/properties/data/properties/description"
      +            },
      +            "severity": {
      +              "description": "low, medium, high or critical",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "sampleRecordingId": {
      +        "$ref": "#/properties/result/properties/data/properties/description"
      +      },
      +      "sessions": {
      +        "items": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "atSeconds": {
      +              "$ref": "#/properties/result/properties/data/properties/occurrences/items/properties/atSeconds"
      +            },
      +            "recordingId": {
      +              "$ref": "#/properties/result/properties/data/properties/description"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "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"
      +  },
      +  "status": {
      +    "description": "\"success\" on every successful call",
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / result / required
      Added value: +[
      +  "status",
      +  "data"
      +]
    • addedOutput schema / properties / result / type
      Added value: +"object"
    • addedOutput schema / required
      Added value: +[
      +  "result"
      +]
  2. 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."
  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 the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial context beyond them: exact error strings for unknown or cross-website ids, the free-trial cap of ten issues, the auth requirement (websiteId or domain plus workspace token), and a privacy constraint that no names, emails, or locations are returned. These are the kinds of operational and data-boundary details annotations cannot express.

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?

The most decision-relevant content is front-loaded (what you get, then when to use it, then failure and auth constraints). The session-field enumeration in the middle is somewhat dense and partly redundant with the existing output schema, but no sentence is filler.

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 four-parameter read tool with an output schema, this covers everything an agent needs: data provenance for the required id, auth requirements, workspace scoping via sibling tooling, failure modes, and a note on what data is absent for privacy reasons. Even though return shape is documented by the output schema, the description's summary of session fields adds useful framing.

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 would be 3, but the description adds provenance and coupling that the schema does not: issueId must come from list_issues, and websiteId/domain are tied to the workspace-token authentication mode. It stops short of explaining workspaceId scoping in the description itself, leaving that entirely to the schema.

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 names a specific verb and resource ('Get full detail for one AI-detected issue') and then enumerates exactly what 'full detail' means: occurrences with timestamps, sessions, replication steps, comments, and linked Linear/Jira tickets. It explicitly contrasts itself with the sibling list_issues, so an agent can distinguish the two without inspecting schemas.

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 gives both the selection rule and the exclusion: 'Get issueId from list_issues; use this only when you need the evidence behind one issue.' That names the alternative tool, the prerequisite for obtaining the id, and the condition under which this tool is warranted. Failure conditions (unknown id, cross-website id, free-trial issue limit) further bound correct usage.

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