Skip to main content
Glama
nulab

Backlog MCP Server

update_wiki

Modify an existing wiki page by updating its name, content, or notification settings using its wiki ID.

Instructions

Updates an existing wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wikiIdYesWiki ID
nameNoName of the wiki page
contentNoContent of the wiki page
mailNotifyNoWhether to send notification emails (default: false)
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • Main handler function for the update_wiki tool. Receives backlog client and translation helper, returns a ToolDefinition with the handler that calls backlog.patchWiki() to update an existing wiki page.
    export const updateWikiTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof updateWikiSchema>,
      (typeof WikiSchema)['shape']
    > => {
      return {
        name: 'update_wiki',
        description: t(
          'TOOL_UPDATE_WIKI_DESCRIPTION',
          'Updates an existing wiki page'
        ),
        schema: z.object(updateWikiSchema(t)),
        outputSchema: WikiSchema,
        importantFields: ['id', 'name', 'content', 'updatedUser'],
        handler: async ({ wikiId, name, content, mailNotify }) => {
          const wikiIdNumber =
            typeof wikiId === 'string' ? parseInt(wikiId, 10) : wikiId;
    
          return backlog.patchWiki(wikiIdNumber, {
            name,
            content,
            mailNotify,
          });
        },
      };
  • Input schema for update_wiki: wikiId (required, string or number), name (optional string), content (optional string), mailNotify (optional boolean).
    const updateWikiSchema = buildToolSchema((t) => ({
      wikiId: z
        .union([z.string(), z.number()])
        .describe(t('TOOL_UPDATE_WIKI_ID', 'Wiki ID')),
      name: z
        .string()
        .optional()
        .describe(t('TOOL_UPDATE_WIKI_NAME', 'Name of the wiki page')),
      content: z
        .string()
        .optional()
        .describe(t('TOOL_UPDATE_WIKI_CONTENT', 'Content of the wiki page')),
      mailNotify: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_WIKI_MAIL_NOTIFY',
            'Whether to send notification emails (default: false)'
          )
        ),
    }));
  • Registration of updateWikiTool in the 'wiki' toolset. It is listed as one of the wiki-related tools.
    {
      name: 'wiki',
      description: 'Tools for managing wiki pages.',
      enabled: false,
      tools: [
        getWikiPagesTool(backlog, helper),
        getWikisCountTool(backlog, helper),
        getWikiTool(backlog, helper),
        addWikiTool(backlog, helper),
        updateWikiTool(backlog, helper),
      ],
    },
Behavior2/5

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

Annotations are absent, so the description must fully reveal behavioral traits. It only states that it updates, but does not disclose side effects, return values, permission requirements, or whether partial updates are supported.

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?

The description is extremely concise (4 words) and front-loaded with the action. While minimal, it is not verbose and communicates the core purpose efficiently.

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 5 parameters and no output schema or annotations, the description is too brief. It omits behavioral details, error conditions, and explanations of how parameters like 'mailNotify' or 'organization' interact.

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?

Input schema has 100% description coverage for all 5 parameters. The description adds no additional meaning beyond the schema definitions, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Updates an existing wiki page' clearly states the action (updates) and the resource (existing wiki page). It effectively distinguishes this tool from sibling tools like 'add_wiki' (creates) and 'get_wiki' (reads).

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 or when alternatives might be better. It does not mention prerequisites (e.g., wikiId must refer to an existing page) or exclusions.

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/nulab/backlog-mcp-server'

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