Skip to main content
Glama

create_group_wiki_page

Generate a new wiki page for a GitLab group by specifying title, content, format, and group ID. Simplify documentation management within GitLab projects.

Instructions

Create a new wiki page for a GitLab group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentNo
formatNo
group_idNo
titleNo

Implementation Reference

  • MCP server tool handler: parses input schema, calls GitLab API helper, and formats response.
    case "create_group_wiki_page": {
      const args = CreateGroupWikiPageSchema.parse(request.params.arguments);
      const wikiPage = await gitlabApi.createGroupWikiPage(args.group_id, {
        title: args.title,
        content: args.content,
        format: args.format
      });
      return formatWikiPageResponse(wikiPage);
    }
  • Zod input schema validation for tool parameters: group_id, title, content, optional format.
    export const CreateGroupWikiPageSchema = z.object({
      group_id: z.string(),
      title: z.string(),
      content: z.string(),
      format: WikiPageFormatEnum.optional()
    });
  • src/index.ts:243-246 (registration)
    Tool registration in ALL_TOOLS: defines name, description, input schema, and read-only flag.
    name: "create_group_wiki_page",
    description: "Create a new wiki page for a GitLab group",
    inputSchema: createJsonSchema(CreateGroupWikiPageSchema),
    readOnly: false
  • GitLab API client method: POST request to /groups/{group_id}/wikis endpoint to create wiki page.
    async createGroupWikiPage(
      groupId: string,
      options: {
        title: string;
        content: string;
        format?: WikiPageFormat;
      }
    ): Promise<GitLabWikiPage> {
      const response = await fetch(
        `${this.apiUrl}/groups/${encodeURIComponent(groupId)}/wikis`,
        {
          method: "POST",
          headers: {
            Authorization: `Bearer ${this.token}`,
            "Content-Type": "application/json",
          },
          body: JSON.stringify({
            title: options.title,
            content: options.content,
            format: options.format || "markdown",
          }),
        }
      );
    
      if (!response.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `GitLab API error: ${response.statusText}`
        );
      }
    
      // Parse the response JSON
      const wikiPage = await response.json();
    
      // Validate and return the response
      return GitLabWikiPageSchema.parse(wikiPage);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a write operation ('Create') but doesn't disclose permissions needed, whether it's idempotent, error handling, or what happens on success (e.g., returns a page ID). This is inadequate for a mutation tool with zero 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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 mutation tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks details on parameters, behavioral traits, usage context, and expected outcomes, making it insufficient for an agent to reliably invoke the tool without external knowledge.

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?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'group_id', 'title', 'content', or 'format' represent, their constraints, or how they interact. The enum for 'format' is documented in the schema but not explained in the description, leaving semantics unclear.

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 ('Create a new wiki page') and target resource ('for a GitLab group'), distinguishing it from sibling tools like 'create_project_wiki_page' by specifying the group context. However, it doesn't explicitly mention what distinguishes it from 'edit_group_wiki_page' or other wiki-related tools beyond the creation aspect.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing group permissions), when not to use it (e.g., for updating existing pages), or direct alternatives like 'create_project_wiki_page' for project-level wikis, leaving the agent to infer usage from context alone.

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