Laraue Boards

edit_issue

Fully replaces an issue's text content - not an append or merge. Fetch the existing content via get_issue first if you need to preserve any of it. Also requires the title - pass the current one (from get_issue) to keep it. Does not change status. Requires canEdit (see get_issue/list_issues).

Input Schema

TableJSON Schema

Name	Required	Description
`files`	No	Files to attach, base64-encoded - each becomes a new attachment, in addition to the issue's existing ones. Same format as create_issue.
`title`	Yes	The issue's title: a short one-line summary, max 256 characters. Required - pass the current title to keep it.
`content`	Yes	The issue's complete new text content, replacing what's there now, max 4096 characters.
`issueKey`	Yes	The issue's key, e.g. 'BRD-42'.
`assigneeId`	No	User id to reassign the issue to, from list_members. Must belong to the caller's organization. Omit to leave the current assignee unchanged.
`attributes`	No	Attribute id -> plain-text value, same format as create_issue. Omit to leave every attribute untouched; pass {} to clear all of them.
`removeAttachmentIds`	No	Ids of existing attachments to remove, from get_issue's Attachments list. Can be combined with files to replace one attachment with another.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 4, 2026

changedInput schema / properties / content / description

Previous value: -"The issue's complete new text content, replacing what's there now."New value: +"The issue's complete new text content, replacing what's there now, max 4096 characters."

addedInput schema / properties / content / maxLength
```
Added value: +4096
```
addedInput schema / properties / title / maxLength
```
Added value: +256
```

Changed2 schema fields changedOct 1, 2026

addedInput schema / properties / title

Added value: +{
+  "description": "The issue's title: a short one-line summary, max 256 characters. Required - pass the current title to keep it.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "issueKey",
-  "content"
-]New value: +[
+  "issueKey",
+  "content",
+  "title"
+]

Changed5 schema fields changedSep 23, 2026

addedInput schema / properties / assigneeId

Added value: +{
+  "default": null,
+  "description": "User id to reassign the issue to, from list_members. Must belong to the caller's organization. Omit to leave the current assignee unchanged.",
+  "format": "uuid",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedInput schema / properties / attributes / description

Previous value: -"Attribute id -> plain-text value, e.g. {\"5\": \"7\"}. Call list_attributes first for the ids/types/expected format per attribute - for a List-typed attribute, the value is one of its list value ids (also from list_attributes), not its display text. Omit entirely to leave every attribute untouched; pass an empty object {} to clear every attribute the issue currently has."New value: +"Attribute id -> plain-text value, same format as create_issue. Omit to leave every attribute untouched; pass {} to clear all of them."

changedInput schema / properties / content / description

Previous value: -"The issue's complete new text content. Fully replaces the existing content - fetch it via get_issue first if you need to preserve any of it."New value: +"The issue's complete new text content, replacing what's there now."

changedInput schema / properties / files / description

Previous value: -"Files to attach, in addition to the issue's existing ones. Same base64 format as create_issue."New value: +"Files to attach, base64-encoded - each becomes a new attachment, in addition to the issue's existing ones. Same format as create_issue."

changedInput schema / properties / removeAttachmentIds / description

Previous value: -"Ids of existing attachments to remove, from get_issue's Attachments list. Can be combined with files to replace an attachment with another."New value: +"Ids of existing attachments to remove, from get_issue's Attachments list. Can be combined with files to replace one attachment with another."

Changed4 schema fields changedSep 23, 2026

changedInput schema / properties / attributes / description

Previous value: -"Attribute name -> plain-text value, same as create_issue. Omit to leave every attribute untouched (not cleared)."New value: +"Attribute id -> plain-text value, e.g. {\"5\": \"7\"}. Call list_attributes first for the ids/types/expected format per attribute - for a List-typed attribute, the value is one of its list value ids (also from list_attributes), not its display text. Omit entirely to leave every attribute untouched; pass an empty object {} to clear every attribute the issue currently has."

changedInput schema / properties / content / description

Previous value: -"The issue's new text content, replacing what's there now."New value: +"The issue's complete new text content. Fully replaces the existing content - fetch it via get_issue first if you need to preserve any of it."

addedInput schema / properties / files

Added value: +{
+  "default": null,
+  "description": "Files to attach, in addition to the issue's existing ones. Same base64 format as create_issue.",
+  "items": {
+    "properties": {
+      "base64Content": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "contentType": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "fileName": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "fileName",
+      "contentType",
+      "base64Content"
+    ],
+    "type": [
+      "object",
+      "null"
+    ]
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedInput schema / properties / removeAttachmentIds

Added value: +{
+  "default": null,
+  "description": "Ids of existing attachments to remove, from get_issue's Attachments list. Can be combined with files to replace an attachment with another.",
+  "items": {
+    "format": "uuid",
+    "type": "string"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

First observedSep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and mostly delivers: it discloses destructive replacement semantics (not append/merge), the pre-fetch workflow to avoid data loss, the required title to preserve, an explicit permission prerequisite (canEdit), and the scope limit (status unchanged). It stops short of stating what happens to existing attachments or attribute side effects, but the core mutation risk profile is well disclosed.

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?

Five short sentences, zero filler, and the most important fact (full replacement, not merge) is front-loaded before the workflow and permission notes. Every sentence adds a distinct constraint or behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter mutation tool with no annotations and no output schema, the description covers the critical gaps: replacement semantics, the destructive data-loss risk, the canEdit requirement, and the status boundary. Attachment and attribute handling are left entirely to the (fully covered) schema, which is a minor gap given the tool's complexity.

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%, so the schema already documents all seven parameters, including the title-preservation note and attachment/attribute semantics. The description's title guidance largely duplicates the schema's own 'Required - pass the current title to keep it' text, adding little beyond the baseline. Baseline 3 is appropriate.

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 opens with a specific verb+resource ('Fully replaces an issue's text content') and immediately disambiguates the operation type ('not an append or merge'). It also separates the tool from the sibling edit_issue_status by stating 'Does not change status.' An agent can distinguish it from edit_comment, create_issue, and edit_issue_status without opening any schema.

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?

Explicit routing guidance: fetch get_issue first if content must be preserved, pass the current title from get_issue to keep it, and requires canEdit (pointing at get_issue/list_issues for the check). It also names the boundary condition (no status change) that would otherwise push the agent to edit_issue_status.

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

All Laraue Boards tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

edit_issue

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources