@@ -616,13 +616,15 @@ The following sets of tools are available:
 
 ## Tools
 
-Repository tools expose output schemas and typed `structuredContent` to clients using MCP protocol `2026-07-28` or later. Older clients, or clients with an unknown protocol version, receive the existing content without an output schema or structured output.
+Repository tools expose output schemas and typed `structuredContent` when the negotiated MCP protocol version is a supported version `2026-07-28` or newer. Older clients, clients with an unknown protocol version, and clients omitting the version receive the existing content without an output schema or structured output. Unknown versions are not treated as supported merely because they sort after `2026-07-28`.
 
 For `get_file_contents`, directory results (including field projections) are structured arrays. File downloads and metadata-only responses use a `content` array of typed text, embedded-resource, or resource-link blocks, preserving status messages, text, base64 blobs, empty files, and download links. Text-only repository mutations such as starring and deletion also return a structured `message`; fork responses distinguish a repository reference from an in-progress message. Repository deletion still requires its existing confirmation flow before returning a completed result.
 
 Structured repository results use compact DTOs rather than raw REST objects. Release lookups share the compact release shape with release listings; Git references retain the ref, object type, and SHA; annotated tags retain tag/message/tagger/target information; deletion commits retain SHA, message, authors, tree SHA, parent SHAs, and a human-facing `html_url` when available. Directory entries retain file metadata and useful HTML/download links, but omit API and hypermedia routing URLs even when those fields were requested in a projection. Legacy and unknown protocol versions retain the original text byte-for-byte; modern text-only JSON responses serialize the same compact DTO as `structuredContent`. Non-text resource blocks and tool errors retain their existing content behavior. Structured projections use the same sanitized and filtered source as the legacy formatter.
 
-The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issue_comment`, `update_issue_comment`), dependency (`issue_dependency_read`, `issue_dependency_write`), and duplicate-detection (`find_duplicate`) tools provide typed `outputSchema` and `structuredContent` for protocol `2026-07-28` and newer. Older or unknown protocol versions retain the same text responses without these fields. Tool errors do not return structured content. Dependency and duplicate-detection tools retain their existing feature gates.
+The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issue_comment`, `update_issue_comment`), dependency (`issue_dependency_read`, `issue_dependency_write`), and duplicate-detection (`find_duplicate`) tools provide typed `outputSchema` and `structuredContent` for negotiated supported protocol versions `2026-07-28` or newer. Older or unknown protocol versions retain the same text responses without these fields. Tool errors do not return structured content. Dependency and duplicate-detection tools retain their existing feature gates.
+
+For negotiated supported protocol versions `2026-07-28` or newer, the consolidated Actions tools (`actions_list`, `actions_get`, `actions_run_trigger`) return structured objects with a `method` discriminant and a method-specific typed field; JSON text contains the same compact projection. Workflow, job, and artifact projections omit API/hypermedia URLs while retaining browser links and useful identifiers, states, timestamps, and usage durations. Run usage lists billable runner environments in deterministic name order. Older and unknown-protocol text responses remain unchanged; `get_job_logs` retains its typed content, URL, or failed-job collection variants.
 
 <!-- START AUTOMATED TOOLS -->
 <details>
@@ -631,7 +633,7 @@ The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issu
 
 - **actions_get** - Get details of GitHub Actions resources (workflows, workflow runs, jobs, and artifacts)
   - **OAuth Challenge Scopes**: `repo`
-  - `method`: The method to execute Supported values: get_workflow, get_workflow_run, get_workflow_job, download_workflow_run_artifact, get_workflow_run_usage, get_workflow_run_logs_url. (string, required)
+  - `method`: The method to execute (string, required)
   - `owner`: Repository owner (string, required)
   - `repo`: Repository name (string, required)
   - `resource_id`: The unique identifier of the resource. This will vary based on the "method" provided, so ensure you provide the correct ID:
@@ -643,7 +645,7 @@ The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issu
 
 - **actions_list** - List GitHub Actions workflows in a repository
   - **OAuth Challenge Scopes**: `repo`
-  - `method`: The action to perform Supported values: list_workflows, list_workflow_runs, list_workflow_jobs, list_workflow_run_artifacts. (string, required)
+  - `method`: The action to perform (string, required)
   - `owner`: Repository owner (string, required)
   - `page`: Page number for pagination (default: 1) (number, optional)
   - `perPage`: Results per page for pagination (default: 30, max: 100) (number, optional)
@@ -653,13 +655,13 @@ The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issu
     - Provide a workflow ID or workflow file name (e.g. ci.yaml) for 'list_workflow_runs' method, or omit to list all workflow runs in the repository.
     - Provide a workflow run ID for 'list_workflow_jobs' and 'list_workflow_run_artifacts' methods.
      (string, optional)
-  - `workflow_jobs_filter`: Filters for workflow jobs. **ONLY** used when method is 'list_workflow_jobs' (object | any, optional)
-  - `workflow_runs_filter`: Filters for workflow runs. **ONLY** used when method is 'list_workflow_runs' (object | any, optional)
+  - `workflow_jobs_filter`: Filters for workflow jobs. **ONLY** used when method is 'list_workflow_jobs' (object, optional)
+  - `workflow_runs_filter`: Filters for workflow runs. **ONLY** used when method is 'list_workflow_runs' (object, optional)
 
 - **actions_run_trigger** - Trigger GitHub Actions workflow actions
   - **OAuth Challenge Scopes**: `repo`
   - `inputs`: Inputs the workflow accepts. Only used for 'run_workflow' method. (object, optional)
-  - `method`: The method to execute Supported values: run_workflow, rerun_workflow_run, rerun_failed_jobs, cancel_workflow_run, delete_workflow_run_logs. (string, required)
+  - `method`: The method to execute (string, required)
   - `owner`: Repository owner (string, required)
   - `ref`: The git reference for the workflow. The reference can be a branch or tag name. Required for 'run_workflow' method. (string, optional)
   - `repo`: Repository name (string, required)
 
@@ -60,10 +60,12 @@ return ghErrors.NewGitHubGraphQLErrorResponse(ctx, message, err), nil
 ### Typed Tool Results
 
 Tools registered with concrete `NewTool[In, Out]` types expose output schemas and
-`structuredContent` only when the negotiated protocol is `2026-07-28` or newer.
-Older or unknown protocols retain the original text responses without these
-typed-output additions. Ordinary API and validation errors never expose the
-SDK-generated zero-value structured output.
+`structuredContent` when the negotiated protocol version is a supported version
+`2026-07-28` or newer. Older, unknown, or omitted protocol versions retain the
+original text responses without these typed-output additions. Unknown versions
+are not treated as supported merely because they sort after `2026-07-28`.
+Ordinary API and validation errors never expose the SDK-generated zero-value
+structured output.
 
 Handler-provided structured statuses are distinct from generated error output.
 For example, `issue_write` can return `IsError: true` with