Skip to main content
Glama
nulab

Backlog MCP Server

get_wiki_pages

Search and retrieve wiki pages from a Backlog project by project ID, key, or keyword.

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
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function that executes the get_wiki_pages tool logic. It accepts optional projectId, projectKey, and keyword, resolves the project identifier using resolveIdOrKey, and calls backlog.getWikis() to fetch 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,
          });
        },
      };
    };
  • Input schema for the get_wiki_pages tool, defining optional projectId (number), projectKey (string), and keyword (string) parameters.
    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')
        ),
    }));
  • Output schema for get_wiki_pages, defining the shape of a wiki page list item (id, projectId, name, tags, created/updated user info).
    export const WikiListItemSchema = z.object({
      id: z.number(),
      projectId: z.number(),
      name: z.string(),
      tags: z.array(TagSchema),
      createdUser: UserSchema,
      created: z.string(),
      updatedUser: UserSchema,
      updated: z.string(),
    });
  • Registration of get_wiki_pages in the 'wiki' toolset group (currently disabled), where getWikiPagesTool is called with backlog and helper instances.
    {
      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),
      ],
    },
  • Helper utility used by the handler to resolve either projectId or projectKey into a single value for the Backlog API call.
    export const resolveIdOrKey = <E extends EntityName>(
      entity: E,
      values: { id?: number; key?: string },
      t: TranslationHelper['t']
    ): ResolveResult => resolveIdOrField(entity, 'key', values, t);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Returns list of Wiki pages' without revealing any behavioral traits such as read-only nature, pagination, authentication requirements, or whether it returns all pages or filtered ones.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one short sentence) but lacks structure and depth. It could benefit from more detail without becoming verbose, but as it stands it is minimally acceptable.

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 4 optional parameters and no output schema, the description is incomplete. It does not explain pagination, result format, or whether multiple filter parameters combine. This leaves significant gaps for the agent.

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 parameters are already documented. The tool description adds no additional meaning beyond what the schema provides, such as how parameters interact or usage patterns. Baseline 3 is appropriate.

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 verb 'Returns' and the resource 'list of Wiki pages', making the purpose straightforward. However, it does not differentiate from sibling tools like 'get_wiki' which might return a single page, but the name implies plurality, so it's clear enough.

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 such as 'get_wiki' or 'get_wikis_count'. There is no mention of prerequisites, filters, or context that would help an agent choose appropriately.

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