Skip to main content
Glama

create_wiki_pages_batch

Create multiple wiki pages simultaneously in Azure DevOps to manage bulk documentation updates efficiently.

Instructions

Create multiple wiki pages at once for bulk operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesThe name or ID of the project.
wiki_identifierYesThe name or ID of the wiki.
pages_dataYesArray of page objects to create.

Implementation Reference

  • The main handler function that implements the batch wiki page creation by iterating through pages_data and calling create_wiki_page for each, returning a list of results with success/error status.
    def create_wiki_pages_batch(self, project, wiki_identifier, pages_data):
        """
        Create multiple wiki pages at once.
        pages_data: list of {"path": str, "content": str}
        """
        results = []
        for page_data in pages_data:
            try:
                result = self.create_wiki_page(
                    project=project,
                    wiki_identifier=wiki_identifier,
                    path=page_data["path"],
                    content=page_data["content"]
                )
                results.append({
                    "path": page_data["path"],
                    "status": "success",
                    "result": result
                })
            except Exception as e:
                results.append({
                    "path": page_data["path"],
                    "status": "error",
                    "error": str(e)
                })
        
        return results
  • The input schema definition for the create_wiki_pages_batch tool, specifying parameters project, wiki_identifier, and pages_data as an array of path/content objects.
    types.Tool(
        name="create_wiki_pages_batch",
        description="Create multiple wiki pages at once for bulk operations.",
        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."
                },
                "pages_data": {
                    "type": "array",
                    "description": "Array of page objects to create.",
                    "items": {
                        "type": "object",
                        "properties": {
                            "path": {
                                "type": "string",
                                "description": "The path of the wiki page to create."
                            },
                            "content": {
                                "type": "string",
                                "description": "The content of the wiki page."
                            }
                        },
                        "required": ["path", "content"]
                    }
                },
            },
            "required": ["project", "wiki_identifier", "pages_data"],
            "additionalProperties": False
        }
    ),
  • The dispatch/registration point in the _execute_tool method where the tool call is routed to the client handler.
    elif name == "create_wiki_pages_batch":
        return self.client.create_wiki_pages_batch(**arguments)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it's for creation but doesn't disclose behavioral traits like required permissions, whether it's idempotent, error handling for partial failures, or rate limits. This is a significant gap for a mutation tool with no annotation coverage.

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 that front-loads the key action ('create multiple wiki pages') and purpose ('for bulk operations'). There is zero wasted wording, making it highly concise and well-structured.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial details like what happens on success/failure, return values, or any behavioral context. The 100% schema coverage helps with parameters, but overall context for safe and effective use is inadequate.

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 fully documents the three parameters. The description adds no additional meaning beyond implying 'pages_data' is for bulk operations, which is already clear from the schema's array structure. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('create') and resource ('multiple wiki pages') with the specific context of 'bulk operations.' It distinguishes from single-page creation tools like 'create_wiki_page' by emphasizing batch capability, though it doesn't explicitly name alternatives.

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

Usage Guidelines3/5

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

The description implies usage for bulk operations, which suggests when to use this over single-page tools, but it doesn't provide explicit guidance on prerequisites, limitations, or when not to use it. No alternative tools are named, leaving usage context somewhat vague.

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