Skip to main content
Glama
mcp-devops-onpremise

mcp-devops-onpremise

by zwitbaum

Delete wiki page

devops_wiki_page_delete
Destructive

Deletes an existing Azure DevOps wiki page using its wiki identifier and page ID, with an optional comment for the deletion.

Instructions

Delete an existing wiki page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wiki_id": "<wiki_id>",
      "page_id": "<page_id>"
    },
    "name": "devops_wiki_page_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment for deleting the wiki page.
page_idYesWiki page ID.
wiki_idYesWiki identifier (name or ID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedInput schema / properties / organization
      Removed value: -{
      -  "description": "DevOps organization name.",
      -  "type": "string"
      -}
    • removedInput schema / properties / project
      Removed value: -{
      -  "description": "DevOps project name.",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "organization",
      -  "project",
      -  "wiki_id",
      -  "page_id"
      -]New value: +[
      +  "wiki_id",
      +  "page_id"
      +]
  2. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that: it does not say whether the deletion is permanent, whether child/sub-pages are removed, whether page history is recoverable, or what the 'comment' parameter is used for.

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?

One short sentence with no filler, and the operation type is front-loaded. It is appropriately minimal for a simple delete, though the brevity leaves the gaps noted in other dimensions.

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

Completeness3/5

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

The schema is fully documented and annotations carry the destructive flag, so the basics are covered. However, for a destructive mutation there is no mention of irreversibility or side effects, and no output schema exists to explain what a successful delete returns.

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 wiki_id, page_id, and comment are all documented in the schema itself. The description does not add any meaning beyond the schema, which is acceptable at baseline when the schema is fully covered.

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 ('Delete an existing wiki page'), which is unambiguous and matches the title. It does not explicitly distinguish itself from the sibling 'devops_wiki_page_update' or 'devops_wiki_page_create_or_update', but the operation type is clear enough for an agent to select correctly.

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 versus the update or create_or_update siblings, nor any stated preconditions. The agent must infer that this is the tool for permanent removal rather than a soft-delete or rename.

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