Skip to main content
Glama

update_wiki_page

Modify existing wiki pages in Azure DevOps projects by updating content, project details, and page paths to maintain documentation accuracy.

Instructions

Updates an existing wiki page with new content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
pathYesThe path of the wiki page.
contentYesThe content of the wiki page.

Implementation Reference

  • The core handler function that implements the logic for updating a wiki page. It retrieves the current page to get the ETag for optimistic concurrency, then calls the Azure DevOps wiki_client to create or update the page with the new content.
    def update_wiki_page(self, project, wiki_identifier, path, content):
        page = self.wiki_client.get_page(
            project=project,
            wiki_identifier=wiki_identifier,
            path=path
        )
        
        # Try to get ETag from various possible locations
        etag = None
        if hasattr(page, 'eTag'):
            etag = page.eTag
        elif hasattr(page, 'etag'):
            etag = page.etag
        elif hasattr(page, 'e_tag'):
            etag = page.e_tag
        elif hasattr(page, '_etag'):
            etag = page._etag
        elif hasattr(page, 'page') and hasattr(page.page, 'eTag'):
            etag = page.page.eTag
        elif hasattr(page, 'page') and hasattr(page.page, 'etag'):
            etag = page.page.etag
        elif hasattr(page, 'page') and hasattr(page.page, 'e_tag'):
            etag = page.page.e_tag
        
        parameters = {
            "content": content
        }
        return self.wiki_client.create_or_update_page(
            project=project,
            wiki_identifier=wiki_identifier,
            path=path,
            parameters=parameters,
            version=etag
        )
  • Defines the tool schema including name, description, and input schema validation for the update_wiki_page tool, which is registered in the MCP server's tool list.
    types.Tool(
        name="update_wiki_page",
        description="Updates an existing wiki page with new content.",
        inputSchema={
            "type": "object",
            "properties": {
                "project": {
                    "type": "string", 
                    "description": "The name or ID of the project."
                },
                "wiki_identifier": {
                    "type": "string", 
                    "description": "The name or ID of the wiki."
                },
                "path": {
                    "type": "string", 
                    "description": "The path of the wiki page."
                },
                "content": {
                    "type": "string", 
                    "description": "The content of the wiki page."
                },
            },
            "required": ["project", "wiki_identifier", "path", "content"],
            "additionalProperties": False
        }
    ),
  • The registration and dispatch logic in the MCP server's _execute_tool method that handles calls to 'update_wiki_page' by invoking the client method and formatting the response.
    elif name == "update_wiki_page":
        page = self.client.update_wiki_page(**arguments)
        return {
            "path": page.page.path,
            "url": page.page.url,
            "content": page.page.content,
        }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool updates content but fails to mention critical aspects like required permissions, whether changes are reversible, potential side effects (e.g., overwriting existing content), or error handling. This leaves significant gaps for a mutation tool.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It is front-loaded and directly states the tool's purpose, making it easy to parse and understand quickly.

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?

Given the complexity of updating a wiki page (a mutation operation), the lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral traits, error cases, or return values, leaving the agent with incomplete information for safe and effective use.

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?

The schema description coverage is 100%, with all parameters well-documented in the input schema. The description adds no additional meaning beyond implying that 'content' is the new content for the page, which is already clear from the schema. This meets the baseline for high schema coverage.

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 clearly states the verb ('Updates') and resource ('existing wiki page'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'update_wiki_page_safe' or 'create_or_update_wiki_page_smart', which would require explicit comparison to achieve a score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'update_wiki_page_safe' or 'create_wiki_page'. It lacks context about prerequisites, exclusions, or specific scenarios, leaving the agent to infer usage from tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/xrmghost/mcp-azure-devops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server