Skip to main content
Glama

create_wiki_page

Create new wiki pages in Azure DevOps projects to document processes, share knowledge, and maintain team documentation.

Instructions

Creates a new wiki page with specified 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

  • MCP server tool dispatch handler for 'create_wiki_page' that invokes the client method and formats the response.
    elif name == "create_wiki_page":
        page = self.client.create_wiki_page(**arguments)
        return {
            "path": page.page.path,
            "url": page.page.url,
            "content": page.page.content,
        }
  • Tool schema definition including input validation for parameters: project, wiki_identifier, path, content.
    types.Tool(
        name="create_wiki_page",
        description="Creates a new wiki page with specified 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
        }
    ),
  • Core handler function in AzureDevOpsClient that creates a wiki page by calling the Azure DevOps wiki_client.create_or_update_page API.
    def create_wiki_page(self, project, wiki_identifier, path, content):
        parameters = {
            "content": content
        }
        return self.wiki_client.create_or_update_page(
            project=project,
            wiki_identifier=wiki_identifier,
            path=path,
            parameters=parameters,
            version=None
        )
  • MCP server registration handler that lists all tools including 'create_wiki_page' by returning the self.tools list populated earlier.
    @self.server.list_tools()
    async def list_tools() -> List[types.Tool]:
        """Return the list of available tools."""
        logger.info(f"Tools requested - returning {len(self.tools)} tools")
        self.tools_registered = True
        return self.tools
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 this is a creation operation but doesn't mention permissions required, whether it overwrites existing pages, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that gets straight to the point without unnecessary words. It could be slightly more informative, but it's well-structured and front-loaded with the core action.

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 creation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, idempotency, or error cases, nor does it explain what the tool returns. Given the complexity and lack of structured data, more context is needed.

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 description mentions 'specified content' which aligns with the 'content' parameter, but doesn't add meaning beyond what the schema already provides. With 100% schema description coverage, the baseline is 3, as the schema adequately documents all parameters without needing extra explanation in the description.

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 action ('creates') and resource ('new wiki page with specified content'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'create_or_update_wiki_page_smart' or 'create_wiki_pages_batch', which would require more specificity to earn a 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 like 'create_or_update_wiki_page_smart' or 'update_wiki_page', nor does it mention prerequisites or exclusions. This lack of context leaves the agent without clear usage direction.

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