Skip to main content
Glama
flowsery

flowsery

Official

Update Issue Status

update_issue_status
DestructiveIdempotent

Set an issue's status to open, in_progress, resolved, or suspended and return the updated issue. Change only status while keeping title, severity, occurrences, and comments intact.

Instructions

Set an issue's status to open, in_progress, resolved, or suspended and return the updated issue. Only the status changes; title, severity, occurrences, and comments stay, and any status can be set again later, so this is reversible. Confirm which state the user means before calling: resolved asserts the bug is fixed, suspended hides a known non-problem from the default list_issues result. Not a delete: issues cannot be removed through this server. Get issueId from list_issues; an unknown id fails with 'Issue not found', and on a free trial issues beyond the first 10 fail as not included in the current plan. 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>",
      "status": "<status>"
    },
    "name": "update_issue_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoWebsite domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
statusYesNew status. resolved asserts the bug is fixed; suspended hides a known non-problem from default listings; open and in_progress keep it visible
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 full issue detail after the change, with the new status."
    • addedOutput schema / properties / result / properties
      Added value: +{
      +  "data": {
      +    "additionalProperties": true,
      +    "description": "The full issue after the change",
      +    "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. Changed4 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 / status / description
      Previous value: -"New status"New value: +"New status. resolved asserts the bug is fixed; suspended hides a known non-problem from default listings; open and in_progress keep it visible"
    • 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 updated issue with its new status."New value: +"Object with status and data: the full issue detail after the change, with the new status."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds a lot beyond annotations: field-level mutation scope, reversibility ('any status can be set again later'), the exact failure message for a bad id ('Issue not found'), free-trial limits beyond the first 10 issues, and the websiteId/domain + workspace-token auth requirement. The one tension is that annotations declare destructiveHint=true while the description stresses 'this is reversible' and 'Not a delete' — consistent with the narrower definition of destructive updates, but the description could have reconciled the two more directly. Rate limits and pagination are irrelevant here, so the gap is small.

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 action and legal values, then scope, then semantics, then failure modes — a sensible information hierarchy. It is dense but nearly every clause is load-bearing; the only mild redundancy is re-explaining resolved/suspended, which the status field description already covers.

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 state-mutating tool with 5 params, auth branching, and plan gating, the description covers scope, reversibility, id sourcing, error text, and permission requirements; the output schema handles the return value, so 'return the updated issue' suffices. Nothing an agent needs to call this safely is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already documents status semantics, issueId provenance, and the websiteId/domain/workspaceId rules in detail. The description largely restates those (status meaning, 'Get issueId from list_issues', token requirements) rather than adding new syntax or constraints. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Opens with a specific verb and resource ('Set an issue's status') plus the exact enum of legal values, and immediately scopes the blast radius ('Only the status changes; title, severity, occurrences, and comments stay'). It also distinguishes itself from a destructive sibling concept by stating 'Not a delete: issues cannot be removed through this server.'

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?

Gives explicit pre-call guidance ('Confirm which state the user means before calling') and disambiguates the two non-obvious enum values: 'resolved asserts the bug is fixed, suspended hides a known non-problem from the default list_issues result.' It also routes the agent to list_issues to obtain issueId, so the entry point is unambiguous.

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