Accept numeric IDs and return display settings in get_saved_view_work_items

What does this MR do and why?

Updates the shipped get_saved_view_work_items MCP tool, as the MCP tool review board asked on #636789 (notes 4110954702 and 4125506423).

  1. saved_view_id now takes a numeric ID ("42") as well as a global ID. Share URLs carry ?saved_view=42, and list_work_item_saved_views will return numeric IDs.
  2. The tool now returns displaySettings. save_work_item_saved_view replaces the whole display settings value on update, so agents need to read the current value first. Without it, "switch my view to a board" wipes hiddenMetadataKeys, groupOrder and the other keys.
  3. The output doesn't change. savedView.id stays a global ID, because changing an existing output field is a breaking change under the MCP guide. Global IDs from 18.11 callers keep working.

No new tool version: the MCP guide treats a new output field and a wider input as additive.

This MR blocks !265187 (merged). List returns 42, and get rejects 42 until this MR merges. If !265187 (merged) merges first, the list → get flow breaks in between.

Related to #631461

How to set up and validate locally

  1. Create a saved view in a group and note its numeric ID from the ?saved_view= URL param.
  2. Call get_saved_view_work_items with group_id and saved_view_id: "<numeric id>". It returns the view, with id as a global ID and displaySettings included.
  3. Call it again with the global ID. Same result.
  4. Call it with the numeric ID of a saved view from another group. It returns "Saved view not found or inaccessible".

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist.

🤖 Generated with Claude Code

Merge request reports

Loading
Loading