From 627ee548b065ee0ef185f352760479d56f40e302 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 27 Jan 2026 03:29:23 +0000
Subject: [PATCH 1/2] Initial plan


From 756d4d4964d63761458c7e90430c45cfa0eee6b4 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 27 Jan 2026 03:38:48 +0000
Subject: [PATCH 2/2] Fix: Clarify MCP tool call instructions in release
 workflow

- Add explicit instructions that update_release is an MCP tool
- Warn against using bash to write JSON files manually
- Emphasize tool must be called through MCP protocol
- Provide example showing correct tool call syntax

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 .github/workflows/release.lock.yml | 18 +++++++++++++++---
 .github/workflows/release.md       | 18 +++++++++++++++---
 2 files changed, 30 insertions(+), 6 deletions(-)

diff --git a/.github/workflows/release.lock.yml b/.github/workflows/release.lock.yml
index f1d9e304b0..9f12b15a2e 100644
--- a/.github/workflows/release.lock.yml
+++ b/.github/workflows/release.lock.yml
@@ -655,11 +655,21 @@ jobs:
           
           ## Output Format
           
-          **CRITICAL**: You MUST call the `update_release` tool to update the release with the generated highlights:
+          **CRITICAL**: You MUST call the `update_release` MCP tool to update the release with the generated highlights.
+          
+          **HOW TO CALL THE TOOL:**
+          
+          The `update_release` tool is an **MCP (Model Context Protocol) tool**, not a bash command or file operation. To call it:
+          
+          1. **Use the MCP tool call syntax** - The tool is registered as `update_release` (or `safeoutputs___update_release`)
+          2. **DO NOT write JSON files manually** - Writing files like `/tmp/gh-aw/safeoutputs/update_release_001.json` will NOT work
+          3. **DO NOT use bash to simulate tool calls** - The tool must be called through the MCP protocol
+          
+          **Example Tool Call:**
           
           ```javascript
           update_release({
-            tag: "${RELEASE_TAG}",
+            tag: "v0.37.26",
             operation: "prepend",
             body: "## 🌟 Release Highlights\n\n[Your complete markdown highlights here]"
           })
@@ -670,7 +680,9 @@ jobs:
           - `operation` - Must be `"prepend"` to add before existing notes
           - `body` - Complete markdown content (include all formatting, emojis, links)
           
-          **WARNING**: If you don't call the `update_release` tool, the release notes will NOT be updated!
+          **IMPORTANT**: This is a real tool call through MCP, NOT a bash command or file write operation. The tool will automatically write to the correct output file (`/opt/gh-aw/safeoutputs/outputs.jsonl`).
+          
+          **WARNING**: If you don't call the `update_release` tool properly through MCP, the release notes will NOT be updated!
           
           **Documentation Base URLs:**
           - User docs: `https://githubnext.github.io/gh-aw/`
diff --git a/.github/workflows/release.md b/.github/workflows/release.md
index ea0603307a..7928596c78 100644
--- a/.github/workflows/release.md
+++ b/.github/workflows/release.md
@@ -470,11 +470,21 @@ Dependency updates and internal improvements to keep things running smoothly.
 
 ## Output Format
 
-**CRITICAL**: You MUST call the `update_release` tool to update the release with the generated highlights:
+**CRITICAL**: You MUST call the `update_release` MCP tool to update the release with the generated highlights.
+
+**HOW TO CALL THE TOOL:**
+
+The `update_release` tool is an **MCP (Model Context Protocol) tool**, not a bash command or file operation. To call it:
+
+1. **Use the MCP tool call syntax** - The tool is registered as `update_release` (or `safeoutputs___update_release`)
+2. **DO NOT write JSON files manually** - Writing files like `/tmp/gh-aw/safeoutputs/update_release_001.json` will NOT work
+3. **DO NOT use bash to simulate tool calls** - The tool must be called through the MCP protocol
+
+**Example Tool Call:**
 
 ```javascript
 update_release({
-  tag: "${RELEASE_TAG}",
+  tag: "v0.37.26",
   operation: "prepend",
   body: "## 🌟 Release Highlights\n\n[Your complete markdown highlights here]"
 })
@@ -485,7 +495,9 @@ update_release({
 - `operation` - Must be `"prepend"` to add before existing notes
 - `body` - Complete markdown content (include all formatting, emojis, links)
 
-**WARNING**: If you don't call the `update_release` tool, the release notes will NOT be updated!
+**IMPORTANT**: This is a real tool call through MCP, NOT a bash command or file write operation. The tool will automatically write to the correct output file (`/opt/gh-aw/safeoutputs/outputs.jsonl`).
+
+**WARNING**: If you don't call the `update_release` tool properly through MCP, the release notes will NOT be updated!
 
 **Documentation Base URLs:**
 - User docs: `https://githubnext.github.io/gh-aw/`