Skip to main content

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_wiki_tools group integrates Genesis with Azure DevOps Wikis. Search wiki content, list wikis and pages, read page bodies with author and timestamp enrichment, create or update pages, browse the page tree or flat page batches, retrieve git-backed revision history, download attachments into the thread, and inspect page metadata with backing-repository and work-item links. Supports both project wikis and git-backed code wikis.

Key Features

Discover wikis and pages

List wikis in a project, browse the page hierarchy, or enumerate large wikis with paginated flat listings.

Search wiki content

Run full-text search across wiki pages and read highlighted match fragments.

Read pages and history

Fetch page content with created/modified metadata from git history, or list revision commits for a page path.

Attachments and cross-links

Download wiki attachments into the thread and resolve work-item and repository links for a page.

Create and update pages

Publish new wiki pages or replace an existing page body after reading its current version (ETag).

Input Parameters for Each Function

ado_list_wikis

ado_search_wiki

ado_get_wiki_page

ado_get_wiki_page_revisions

ado_get_wiki_page_tree

ado_list_wiki_pages

ado_download_wiki_attachment

ado_get_wiki_page_metadata

ado_create_or_update_wiki_page

Example Usage

Output

  • ado_list_wikis returns wikis (id, name, type — projectWiki or codeWiki — repositoryId, mappedPath) and count.
  • ado_search_wiki returns count and results with path, wiki, project, file_name, content_id, and hits (highlighted fragments).
  • ado_get_wiki_page returns page (markdown/HTML content preserved as stored), wiki, version (page ETag), created_by / created_date and last_modified_by / last_modified_date from git history, content_size_bytes, and content_omitted. Pages larger than 5 MB omit inline content and return download_url and web_url instead. A history_error may appear when git history enrichment fails without failing the read.
  • ado_get_wiki_page_revisions returns revisions (newest first: commit_id, author, committer, message, url), count, page_path, and git_item_path.
  • ado_get_wiki_page_tree returns tree (nested nodes with path, is_parent_page, sub_pages, and git_item_path / id when present) and page_count. No page content is included.
  • ado_list_wiki_pages returns pages (id and path per page), count, and continuation_token for the next batch (null when exhausted).
  • ado_download_wiki_attachment saves the file to the thread and returns file_path, relative_path, file_id, file_name, size, and attachment_path.
  • ado_get_wiki_page_metadata returns page (metadata only), version, wiki, repository (backing git repo), work_items (linked ids and URLs), and links (WorkItem / Repository entries). work_items_error or repository_error may appear when that lookup fails while the rest succeeds.
  • ado_create_or_update_wiki_page returns success, created (true when a new page was created, false when an existing page was updated), page, version (the new ETag — pass it to the next update), and web_url. On failure, success is false with error; HTTP failures may also include status_code (412 means the supplied version was stale or missing — re-read the page and retry; 401 or 403 usually means the PAT lacks Wiki (Read & Write) or the caller lacks contribute permission on the wiki project).

Configuration Details

  • Wiki reads need Wiki (Read) and Code (Read) PAT scopes. Page writes additionally need Wiki (Read & Write). Deleting pages and uploading attachments are not supported.
  • Calls that resolve a project require either an explicit project parameter or a default project on the saved connection.
  • See Azure DevOps for the full PAT scope list.
  • Azure DevOps Services wiki full-text search is served from almsearch.dev.azure.com, so outbound allowlists must include that host.

Limitations or Notes

  1. Use ado_list_wikis first when the wiki name is unknown — every other tool takes wiki as name or id from that listing.
  2. ado_get_wiki_page_tree is best for wikis with roughly up to 1,000 pages. For larger wikis, prefer ado_list_wiki_pages and page in with continuation_token.
  3. Wiki search can lag recent edits. If ado_search_wiki returns no matches, browse with ado_get_wiki_page_tree or list pages with ado_list_wiki_pages.
  4. ado_download_wiki_attachment only fetches files under the wiki’s .attachments folder (up to 100 MB per file). Pass the name from page markdown or the full /.attachments/... path.
  5. ado_get_wiki_page accepts either path or page_id. A 404 means the path does not exist in that wiki — confirm the path with ado_get_wiki_page_tree.
  6. To update a page with ado_create_or_update_wiki_page, read it first with ado_get_wiki_page and pass the returned version. Omit version only when creating a new page. content replaces the entire page body; it is not appended.
  7. Page deletion and attachment upload are not supported in this tool group.
  8. For Confluence documentation use the Confluence connector; for Genesis’s internal wiki use the wiki knowledge tools.