Skip to main content
Glama

delete_project_wiki_page

Remove a wiki page from a GitLab project by specifying the project ID and page slug. Ideal for maintaining clean and updated project documentation.

Instructions

Delete a wiki page from a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNo
slugNo

Implementation Reference

  • MCP tool handler in the CallToolRequest switch statement. Parses arguments using the schema and delegates to gitlabApi.deleteProjectWikiPage, then returns success message.
    case "delete_project_wiki_page": {
      const args = DeleteProjectWikiPageSchema.parse(request.params.arguments);
      await gitlabApi.deleteProjectWikiPage(args.project_id, args.slug);
      return { content: [{ type: "text", text: `Wiki page '${args.slug}' has been deleted.` }] };
  • Core implementation function that performs the actual DELETE request to GitLab API to delete the project wiki page.
    async deleteProjectWikiPage(
      projectId: string,
      slug: string
    ): Promise<void> {
      const response = await fetch(
        `${this.apiUrl}/projects/${encodeURIComponent(projectId)}/wikis/${encodeURIComponent(slug)}`,
        {
          method: "DELETE",
          headers: {
            Authorization: `Bearer ${this.token}`,
          },
        }
      );
    
      if (!response.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `GitLab API error: ${response.statusText}`
        );
      }
    }
  • Zod schema defining input parameters: project_id and slug for the wiki page.
    export const DeleteProjectWikiPageSchema = z.object({
      project_id: z.string(),
      slug: z.string()
    });
  • src/index.ts:218-221 (registration)
    Tool registration in ALL_TOOLS array, defining name, description, input schema, and readOnly flag.
    name: "delete_project_wiki_page",
    description: "Delete a wiki page from a GitLab project",
    inputSchema: createJsonSchema(DeleteProjectWikiPageSchema),
    readOnly: false
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool deletes a wiki page, implying a destructive mutation, but fails to disclose critical behavioral traits such as whether deletion is permanent or reversible, what permissions are required, or any rate limits or side effects. This leaves significant gaps for safe agent usage.

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, straightforward sentence with no wasted words. It is appropriately sized and front-loaded, directly stating the tool's action without unnecessary elaboration, making it efficient for quick understanding.

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 tool's destructive nature (implied by 'Delete'), no annotations, no output schema, and low parameter documentation, the description is incomplete. It lacks essential context such as behavioral details, parameter explanations, and usage guidelines, which are critical for a mutation tool in this environment with sibling tools available.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, with two parameters ('project_id' and 'slug') undocumented. The description does not add any meaning beyond the schema—it does not explain what these parameters represent, their format, or how they identify the wiki page to delete. This fails to compensate for the low 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 action ('Delete') and resource ('a wiki page from a GitLab project'), making the purpose unambiguous. However, it does not differentiate from its sibling 'delete_group_wiki_page', which performs a similar operation on group wikis instead of project wikis, so it misses full sibling distinction.

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. It does not mention prerequisites (e.g., permissions needed), when-not-to-use scenarios, or refer to related tools like 'edit_project_wiki_page' or 'get_project_wiki_page' for other operations on project wiki pages.

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

Related 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/yoda-digital/mcp-gitlab-server'

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