Skip to main content
Glama

delete_wiki_page

Remove a wiki page from Azure DevOps by specifying its path, project, and wiki identifier to manage documentation.

Instructions

Deletes a wiki page by its path.

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 to delete.

Implementation Reference

  • Tool schema definition including input parameters: project, wiki_identifier, path. This is part of the tools list registration.
    types.Tool(
        name="delete_wiki_page",
        description="Deletes a wiki page by its path.",
        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 to delete."
                },
            },
            "required": ["project", "wiki_identifier", "path"],
            "additionalProperties": False
        }
    ),
  • MCP server tool dispatch handler: calls AzureDevOpsClient.delete_wiki_page with arguments and returns success message.
    elif name == "delete_wiki_page":
        self.client.delete_wiki_page(**arguments)
        return {
            "message": f"Wiki page '{arguments['path']}' deleted successfully.",
            "path": arguments['path']
        }
  • Core implementation: invokes Azure DevOps WikiClient.delete_page API to delete the specified wiki page.
    def delete_wiki_page(self, project, wiki_identifier, path):
        return self.wiki_client.delete_page(
            project=project,
            wiki_identifier=wiki_identifier,
            path=path
        )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action ('Deletes') but doesn't mention whether deletion is permanent, reversible, requires specific permissions, affects linked content, or has confirmation steps. For a destructive operation, this is a significant gap in safety and behavioral context.

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, focused sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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 destructive operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion, whether there's confirmation or error handling, or how this tool differs from other wiki modification tools. Given the complexity and risk of deletion, 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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description mentions 'path' but doesn't add any additional semantic context beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 ('Deletes') and resource ('a wiki page by its path'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_work_item' or explain why this specific deletion tool exists versus other wiki modification tools.

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?

No guidance is provided about when to use this tool versus alternatives like 'update_wiki_page_safe' or 'move_wiki_page', nor are prerequisites or warnings mentioned. The description offers only basic functional information without contextual usage advice.

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