Skip to main content
Glama
Tiberriver256

Azure DevOps MCP Server

by Tiberriver256
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_wiki_page

Updates the markdown content of a wiki page in Azure DevOps by specifying the wiki ID, page path, and new content.

Instructions

Update content of a wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiIdYesThe ID or name of the wiki
commentNoOptional comment for the update
contentYesThe new content for the wiki page in markdown format
pagePathYesPath of the wiki page to update
projectIdNoThe ID or name of the project (Default: MyProject)
organizationIdNoThe ID or name of the organization (Default: mycompany)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.6
    • removedInput schema / properties / comment / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / comment / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / organizationId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / organizationId / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / projectId / anyOf
      Removed value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / projectId / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden for a mutation tool. It does not disclose whether the page must already exist, what happens on a path collision, whether updates require permissions, or how the optional comment is used.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the resource front-loaded. It is efficient, though the brevity is partly a result of under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter mutation tool with no annotations and no output schema, the description should explain prerequisites, conflict behavior, and the effect of the optional comment. It omits all of this, leaving the agent with insufficient context to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters (including wikiId, pagePath, content, and the optional comment/projectId/organizationId) are already documented in the schema. The description adds no syntax, format, or defaults beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Update content of a wiki page'), which is clearly distinguishable from read-oriented siblings like get_wiki_page or search_wiki. It does not, however, differentiate itself from create_wiki_page or list_wiki_pages beyond the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus create_wiki_page or get_wiki_page, and no prerequisites or conditions are stated. The agent must infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools