Skip to main content
Glama

Flowsery

by com.flowsery
OverviewDiscussionsAdmin

Update Issue Status

update_issue_status
Destructive

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.

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
resultNoObject with status and data: the full issue detail after the change, with the new status.

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
    • 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"
+}
  3. Changed4 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 / 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."
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing what changes and what is preserved (title, severity, occurrences, comments), that any status can be re-applied later, the required auth (workspace token with websiteId/domain), named failure modes ('Issue not found', free-trial 10-issue limit), and the effect of suspended on list_issues results. The reversibility claim sits in mild tension with destructiveHint=true but adds needed nuance rather than contradicting it.

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-loads the core action and allowed values, then layers constraints and side effects in descending priority; almost every sentence carries actionable content. It is dense and slightly crammed into one paragraph, but nothing is padding.

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 mutation tool with an output schema, it covers everything an agent needs: mutation scope, reversibility, auth requirements, error conditions, plan limits, and the source of required ids. Return values are covered by the output schema, so no gap remains.

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 each parameter already carries an explanation, including the enum semantics for status. The description largely restates what the schema provides (issueId from list_issues, websiteId-or-domain auth) without adding new syntax or format detail, so the baseline 3 applies.

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 (Set) and resource (an issue's status), enumerates the four allowed values, and notes the updated issue is returned. It is clearly distinguishable from siblings list_issues, get_issue, and delete_goals, and it explicitly states what the tool is NOT (a delete).

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 when-to-use guidance: confirm the intended state before calling, with the semantic difference between resolved (bug fixed) and suspended (hidden non-problem). It names the source of issueId (list_issues), the alternative targets (websiteId/domain), and the case where it should not be used (deletion).

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