Overview
Before using this tool group, save an Azure DevOps connection as described in
Azure DevOps. If
connection_id is omitted, the
tools use the effective default azure_devops connection for the current
user (My default, then Role default). Actions that need a project use the
explicit project parameter first and otherwise fall back to the connection’s
saved default project. When multiple role defaults conflict, pass
connection_id explicitly or set a user default. See
Default connection layers.Tool Name
Purpose
The azure_devops_boards_tools group integrates Genesis with Azure DevOps Boards. Create and update work items (including sprint moves), link work items to each other or to pull requests, read single or batched work item details, search with structured filters or WIQL, list sprints and boards, read comments and revision history, inspect links and text attachments, and retrieve sprint capacity for a specific team iteration. Successful agent writes also record best-effort observations on the Requests page when that feature is enabled.Key Features
Create and update work items
Open new Azure DevOps work items, patch standard fields (including sprint
moves via
iteration_path), add comments, and link items to parents,
children, related work, or pull requests.Read issue context
Fetch one work item or up to 100 ids per batch; read comments, revision
history, grouped links, and text attachments.
Query Boards data
Find work items with structured filters (
ado_find_work_items) or
hand-written WIQL (ado_search_work_items).Explore team structure
List iterations (sprints), Kanban boards, and backlog levels for a team.
Inspect sprint capacity
Retrieve team capacity for a specific iteration to support planning.
Track managed work on Requests
When Requests is enabled, agent creates, updates, comments, and links
through the write tools appear on the Activity tab with deep links back to
Azure DevOps. Assignment automation
can also poll for work items assigned to the connection identity and open
orchestrator threads without an explicit agent tool call.
Requests page tracking
When Requests is enabled (GENESIS_SHOW_WORK),
successful agent writes through ado_create_work_item, ado_update_work_item,
and ado_link_work_items record observations in the Genesis ticket ledger.
Each tracked row shows the Azure DevOps state, a normalized Genesis lifecycle
state, the agent executor, the Genesis thread when one exists, and a deep link
to the work item in Azure DevOps. Azure DevOps remains the system of record —
ledger emission is observability only and never affects tool success.
- Work items appear when an agent manages them through these write tools, or when Azure DevOps assignment automation picks up a work item assigned to the connection identity. Genesis does not bulk-import a backlog.
ado_get_work_itemrefreshes provider state for items Genesis already tracks; read-only lookups never import untracked backlog items.- Failed writes against an already-tracked item record an error on its timeline; failed writes against untracked ids are not imported.
- State changes applied through
stateorfields={"System.State": ...}emit status-change events; comment-only updates keep the item in aworkingstate so later observations can close the loop.
Input Parameters for Each Function
ado_create_work_item
ado_update_work_item
ado_update_work_item requires at least one field update or a comment.
When comment is set, Genesis posts through the project-scoped comments API —
pass project or save a default project on the connection. Write operations
require a PAT with Work Items (Read & Write); a read-only PAT returns
error_type: permission.ado_link_work_items
link_type semantics: parent makes target_work_item_id the parent of
work_item_id; child makes it a child; related adds a plain relation;
pull_request attaches the PR named by repo and pull_request_id as an
artifact link. A work item cannot be linked to itself. Requires a PAT with
Work Items (Read & Write).ado_get_work_item
ado_get_work_items_batch
ado_search_work_items
ado_search_work_items returns id/url references in query_result.workItems
only. Fetch full fields with ado_get_work_items_batch. Invalid WIQL returns
error_type: invalid_wiql with the parser message. For common searches
(for example “bugs assigned to me”), prefer ado_find_work_items.ado_find_work_items
ado_list_iterations
ado_list_boards
ado_list_backlogs
ado_get_work_item_comments
ado_get_work_item_history
ado_get_work_item_links
ado_download_attachment
ado_get_sprint_capacity
Workflow/How It Works
- Configure your effective default
azure_devopsconnection in Azure DevOps, or passconnection_id. - Use
ado_create_work_itemto open new tasks, bugs, or other work items. - Use
ado_get_work_item,ado_get_work_items_batch, andado_update_work_itemto inspect and modify existing work (including sprint moves withiteration_path). - Use
ado_link_work_itemsto relate work items or attach a pull request; useado_get_work_item_linksto inspect existing relationships. - Use
ado_find_work_itemsfor structured searches (for example bugs assigned to you in the current sprint) orado_search_work_itemsfor hand-written WIQL. - Use
ado_list_iterations,ado_list_boards, andado_list_backlogsto discover team structure; useado_get_sprint_capacityfor planning data. - Use
ado_get_work_item_comments,ado_get_work_item_history, andado_download_attachmentfor discussion, audit, and attachment context.
Examples
Output
ado_create_work_itemreturns the createdwork_item. Whenparent_idis supplied and creation succeeds, the response can also includenext_stepsthat remind the caller to link the parent work item in Azure DevOps.ado_update_work_itemreturnssuccess: trueplus the updatedwork_itemwhen fields were patched, andcommentwhen a comment was added.ado_link_work_itemsreturnssuccess: true, the updatedwork_item, and thelinkrelation that was added.ado_get_work_itemreturnswork_itemwith every system and custom field.include_relationsadds the raw relations array.ado_get_work_items_batchreturnswork_items,count, andmissing_idsfor ids Azure DevOps did not return (deleted or not visible to the PAT).ado_search_work_itemsreturns the raw Azure DevOpsquery_resultwhoseworkItemsare id/url references only. When you passproject, Genesis also echoesprojectin the response.ado_find_work_itemsreturnswiql,count,work_items(full details by default, or id/url references wheninclude_detailsisfalse), and optionallymissing_idsordetail_fetch_error.ado_list_iterationsreturnsiterationswith id, name, path, and start/finish dates.ado_list_boardsreturnsboardswith id, name, and url.ado_list_backlogsreturnsbacklogswith id, name, rank, and accepted work item types.ado_get_work_item_commentsreturnscomments,count,total_count, andcontinuation_tokenfor paging.ado_get_work_item_historyreturnsrevisions(field snapshots, oldest first) andcount.ado_get_work_item_linksreturns links grouped asparent,children,related,pull_requests,commits,attachments,hyperlinks, andother, plus per-group counts.ado_download_attachmentreturnstext(UTF-8, truncated past 100,000 characters),size_bytes, andtruncated.ado_get_sprint_capacityreturnscapacity.
Configuration Details
fieldsuses Azure DevOps field reference names such asSystem.Title,System.State, orMicrosoft.VSTS.Common.Priority.- Calls that resolve a project require either an explicit
projectparameter or a defaultprojecton the saved connection.
Limitations or Notes
ado_get_work_itemacceptsprojectfor signature consistency; the work item is resolved bywork_item_id. Onado_update_work_item,project(or a connection default) is required whencommentis set because Azure DevOps serves the comments API only under a project URL.- Comment text is never inlined by
ado_get_work_item— useado_get_work_item_commentsfor discussion content. ado_search_work_itemsandado_find_work_items(withinclude_details=false) return id/url references; fetch full records withado_get_work_items_batch(up to 100 ids per call).ado_find_work_itemswithiteration='current'requiresteambecause Azure DevOps resolves the active sprint per team.ado_download_attachmentreads text attachments only. Binary attachments (images, archives, office documents) return an error — open the attachment URL in Azure DevOps instead.parent_idonado_create_work_itemadds a follow-up hint only. Useado_link_work_itemswithlink_type='parent'orlink_type='child'to create the hierarchy after creation.ado_update_work_itemandado_link_work_itemsare write operations. A PAT with Work Items read-only access returnserror_type: permission(Azure DevOps may answer with HTTP 401 for insufficient scope).- Requests-page tracking is best-effort. Ledger emission is guarded so malformed Azure DevOps payloads or ledger unavailability never change tool success responses.

