Skip to main content
Glama
nulab

Backlog MCP Server

get_wiki_pages

Retrieve wiki pages from Backlog projects using project ID, key, or keyword search to access documentation and knowledge resources.

Instructions

Returns list of Wiki pages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')
keywordNoKeyword to search for in Wiki pages

Implementation Reference

  • The handler function that executes the 'get_wiki_pages' tool logic: resolves project ID or key, then calls backlog.getWikis with project and optional keyword.
    handler: async ({ projectId, projectKey, keyword }) => {
      const result = resolveIdOrKey(
        'project',
        { id: projectId, key: projectKey },
        t
      );
      if (!result.ok) {
        throw result.error;
      }
      return backlog.getWikis({
        projectIdOrKey: result.value,
        keyword,
      });
    },
  • Zod schema definition for the input parameters of the 'get_wiki_pages' tool: optional projectId, projectKey, and keyword.
    const getWikiPagesSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_GET_WIKI_PAGES_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_GET_WIKI_PAGES_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
      keyword: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_WIKI_PAGES_KEYWORD', 'Keyword to search for in Wiki pages')
        ),
    }));
  • Registration of the 'get_wiki_pages' tool within the 'wiki' toolset group in the allTools export.
      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),
      ],
    },
  • Tool schema instantiation and output schema (WikiListItemSchema) definition.
    schema: z.object(getWikiPagesSchema(t)),
    outputSchema: WikiListItemSchema,
    importantFields: ['projectId', 'name', 'tags'],
  • Full tool definition export including name, description, schemas, and handler for 'get_wiki_pages'.
    export const getWikiPagesTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof getWikiPagesSchema>,
      (typeof WikiListItemSchema)['shape']
    > => {
      return {
        name: 'get_wiki_pages',
        description: t(
          'TOOL_GET_WIKI_PAGES_DESCRIPTION',
          'Returns list of Wiki pages'
        ),
        schema: z.object(getWikiPagesSchema(t)),
        outputSchema: WikiListItemSchema,
        importantFields: ['projectId', 'name', 'tags'],
        handler: async ({ projectId, projectKey, keyword }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          return backlog.getWikis({
            projectIdOrKey: result.value,
            keyword,
          });
        },
      };
    };
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 only states it 'returns list of Wiki pages'. It doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what happens if parameters are omitted. This is a significant gap for a tool with parameters and no annotations.

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 with zero waste. It's front-loaded and appropriately sized for its purpose, making it easy to parse quickly.

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 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or how parameters influence the list. For a tool with this complexity, more context is needed to guide effective use.

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 (projectId, projectKey, keyword). The description adds no meaning beyond the schema, as it doesn't explain how parameters interact or affect results. Baseline 3 is appropriate since the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Returns list of Wiki pages' clearly states the action (returns list) and resource (Wiki pages), which is adequate. However, it doesn't differentiate from sibling tools like 'get_wiki' (singular) or 'get_wikis_count', making it somewhat vague in comparison. It's not tautological but lacks specificity about scope.

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 doesn't mention siblings like 'get_wiki' (for a single page) or 'get_wikis_count' (for counting), nor does it specify prerequisites or contexts for usage. This leaves the agent without clear direction.

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