Skip to main content
Glama
tmhr1850

Backlog MCP Server

getWikiPages

Retrieve wiki page listings from Backlog projects to access documentation and collaborative content for project management and issue tracking.

Instructions

Wikiページ一覧の取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the getWikiPages tool logic: validates parameters using the defined schema, processes the API path 'wikis', calls the Backlog API via fetchFromBacklog, and returns the JSON response as text.
    const handler = async (params: Record<string, unknown>): Promise<McpResponse> => {
      try {
        // パラメータのバリデーション
        const validatedParams = await endpoint.schema.parseAsync(params);
    
        // URL中のプレースホルダーを置換
        let path = endpoint.path;
        
        // URIスキーム(例:space://info)の場合はBacklog APIのパスに変換
        if (path.includes('://')) {
          // URIスキームを取り除いてAPIパスに変換
          const uriParts = path.split('://');
          const resourceType = uriParts[0];
          const resourcePath = uriParts[1];
          
          // リソースタイプに応じてAPIパスを構築
          switch (resourceType) {
            case 'space':
              path = 'space';
              break;
            case 'projects':
              if (resourcePath === 'list') {
                path = 'projects';
              } else {
                path = `projects/${resourcePath}`;
              }
              break;
            case 'issues':
              if (resourcePath.includes('/list')) {
                const projectPart = resourcePath.split('/')[0];
                path = 'issues';
                validatedParams.projectIdOrKey = projectPart;
              } else if (resourcePath.includes('/details')) {
                const issuePart = resourcePath.split('/')[0];
                path = `issues/${issuePart}`;
              }
              break;
            case 'wikis':
              if (resourcePath.includes('/list')) {
                const projectPart = resourcePath.split('/')[0];
                path = 'wikis';
                validatedParams.projectIdOrKey = projectPart;
              }
              break;
            case 'users':
              path = 'users';
              break;
            default:
              path = resourcePath;
          }
        }
        
        // 通常のパスパラメータの置換処理
        for (const [key, value] of Object.entries(validatedParams)) {
          if (typeof value === "string" || typeof value === "number") {
            const placeholder = `{${key}}`;
            if (path.includes(placeholder)) {
              path = path.replace(placeholder, String(value));
              // プレースホルダーとして使用したパラメータは削除
              delete validatedParams[key];
            }
          }
        }
    
        // メソッドの追加
        if (endpoint.method !== "GET") {
          validatedParams.method = endpoint.method;
        }
    
        // APIリクエストの実行
        const data = await fetchFromBacklog(path, validatedParams);
        return {
          content: [{ 
            type: "text" as const, 
            text: JSON.stringify(data, null, 2) 
          }],
        };
      } catch (error: any) {
        // エラーメッセージの整形
        const errorMessage = error.errors 
          ? `バリデーションエラー: ${JSON.stringify(error.errors)}`
          : `エラー: ${error.message}`;
    
        return {
          content: [{ 
            type: "text" as const, 
            text: errorMessage 
          }],
          isError: true,
        };
      }
    };
  • Zod input schema for getWikiPages tool parameters (projectIdOrKey, keyword, sort, order, offset, count) and endpoint configuration (path: 'wikis').
    name: "getWikiPages",
    description: "Wikiページ一覧の取得",
    path: "wikis",
    method: "GET",
    schema: z.object({ 
      projectIdOrKey: projectIdOrKeySchema.optional(),
      keyword: z.string().max(1000, "検索キーワードは1000文字以内である必要があります").optional(),
      sort: sortSchema.optional(),
      order: orderSchema.optional(),
      offset: offsetSchema,
      count: countSchema,
    }),
    type: "tool",
  • Registers the getWikiPages tool (and other tools) with the MCP server using server.tool, passing the name, description, and the shared handler function.
    if (endpoint.type === "tool") {
      // ツールの登録
      server.tool(
        endpoint.name,
        endpoint.description,
        async (args: Record<string, unknown>) => handler(args)
      );
    } else if (endpoint.type === "resource") {
  • Helper function called by the handler to make the actual HTTP request to Backlog API endpoint '/wikis' with parameters, handling authentication via env vars, query params, and comprehensive error handling.
    export async function fetchFromBacklog(endpoint: string, params: Record<string, any> = {}): Promise<any> {
      // 環境変数のバリデーション
      const domain = process.env.BACKLOG_DOMAIN;
      const apiKey = process.env.BACKLOG_API_KEY;
    
      if (!domain) {
        throw new Error('環境変数 BACKLOG_DOMAIN が設定されていません');
      }
    
      if (!apiKey) {
        throw new Error('環境変数 BACKLOG_API_KEY が設定されていません');
      }
    
      try {
        // パラメータのサニタイズ
        const sanitizedParams: Record<string, any> = {};
        
        // projectIdOrKeyパラメータをprojectIdに変換(互換性のため)
        if (params.projectIdOrKey !== undefined) {
          sanitizedParams.projectId = params.projectIdOrKey;
          delete params.projectIdOrKey;
        }
        
        // その他のパラメータをコピー
        Object.keys(params).forEach(key => {
          if (params[key] !== undefined && params[key] !== null) {
            sanitizedParams[key] = params[key];
          }
        });
    
        // エンドポイントのパスパラメータを置換
        let processedEndpoint = endpoint;
        const pathParams = processedEndpoint.match(/:([a-zA-Z0-9_]+)/g) || [];
        
        for (const param of pathParams) {
          const paramName = param.substring(1); // :を除去
          if (sanitizedParams[paramName] === undefined) {
            throw new Error(`パスパラメータ ${paramName} が指定されていません`);
          }
          
          processedEndpoint = processedEndpoint.replace(param, sanitizedParams[paramName]);
          delete sanitizedParams[paramName];
        }
    
        // リクエストURLの構築
        const baseUrl = `https://${domain}/api/v2/${processedEndpoint}`;
        const isPost = processedEndpoint.includes('POST');
        
        let url = baseUrl;
        let requestOptions: RequestInit = {
          headers: {
            'Content-Type': 'application/json',
          },
        };
    
        // GETリクエストの場合はクエリパラメータを追加
        if (!isPost) {
          const queryParams = new URLSearchParams();
          queryParams.append('apiKey', apiKey);
          
          Object.keys(sanitizedParams).forEach(key => {
            if (Array.isArray(sanitizedParams[key])) {
              sanitizedParams[key].forEach((value: any) => {
                queryParams.append(`${key}[]`, value.toString());
              });
            } else {
              queryParams.append(key, sanitizedParams[key].toString());
            }
          });
          
          url = `${baseUrl}?${queryParams.toString()}`;
        } else {
          // POSTリクエストの場合はボディにパラメータを設定
          requestOptions.method = 'POST';
          requestOptions.body = JSON.stringify(sanitizedParams);
          url = `${baseUrl}?apiKey=${apiKey}`;
        }
    
        // デバッグ用ログ(開発時のみ)
        if (process.env.NODE_ENV === 'development') {
          console.debug(`Backlog API リクエスト: ${url}`);
          console.debug('パラメータ:', sanitizedParams);
        }
    
        // APIリクエストの実行
        const response = await fetch(url, requestOptions);
        
        // レスポンスのステータスコードチェック
        if (!response.ok) {
          const errorText = await response.text();
          let errorMessage = `Backlog API エラー: HTTP ${response.status}`;
          
          try {
            const errorJson = JSON.parse(errorText);
            if (isBacklogError(errorJson)) {
              const error = errorJson.errors[0];
              errorMessage = `Backlog API呼び出しエラー: Backlogエラー [${error.code}]: ${error.message}${error.moreInfo ? ` - ${error.moreInfo}` : ''}`;
            }
          } catch (e) {
            errorMessage += ` - ${errorText}`;
          }
          
          throw new Error(errorMessage);
        }
    
        // レスポンスのJSONパース
        try {
          const data = await response.json();
          
          // Backlogエラーのチェックとエラーメッセージのフォーマット
          if (isBacklogError(data)) {
            const error = data.errors[0];
            throw new Error(`Backlog API呼び出しエラー: Backlogエラー [${error.code}]: ${error.message}${error.moreInfo ? ` - ${error.moreInfo}` : ''}`);
          }
          
          return data;
        } catch (error) {
          if (error instanceof SyntaxError) {
            throw new Error(`Backlog API呼び出しエラー: JSONパースエラー - ${error.message}`);
          }
          throw error;
        }
      } catch (error) {
        // ネットワークエラーなどの例外処理
        if (error instanceof TypeError && error.message.includes('fetch')) {
          throw new Error(`Backlog API接続エラー: ${error.message}`);
        }
        
        // タイムアウトエラー
        if (error instanceof Error && error.name === 'AbortError') {
          throw new Error('Backlog APIタイムアウトエラー: リクエストがタイムアウトしました');
        }
        
        // その他のエラーはそのまま再スロー
        throw error;
      }
  • server.ts:29-29 (registration)
    Top-level call to register all MCP tools including getWikiPages by invoking registerEndpoints on the MCP server instance.
    registerEndpoints(server);
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 states this is a retrieval operation ('取得'), implying it's likely read-only, but doesn't confirm this or describe any other behavioral traits such as authentication requirements, rate limits, pagination behavior, error conditions, or what '一覧' (list) entails structurally. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 - a single Japanese phrase that directly states the tool's purpose. There's no wasted language or unnecessary elaboration. However, the lack of English translation or additional context might reduce effectiveness for some agents, and it could benefit from being more front-loaded with essential details if this were a more complex tool.

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 simplicity (0 parameters, no output schema), the description is minimally complete but inadequate for full understanding. While it states what the tool does, it doesn't provide enough context about the return format (what a 'wiki page list' contains), behavioral constraints, or how it fits with sibling tools. For even a simple retrieval tool, more information about the expected output and usage context would be helpful.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage (empty schema). The description doesn't need to compensate for any parameter documentation gaps since there are none. It appropriately doesn't mention parameters, which aligns with the schema. The baseline for 0 parameters is 4, as the description correctly focuses on the tool's purpose rather than non-existent parameters.

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 'Wikiページ一覧の取得' (Get list of wiki pages) clearly states the verb ('取得' - get) and resource ('Wikiページ一覧' - wiki page list), making the purpose understandable. However, it doesn't distinguish this tool from potential sibling wiki tools (none exist in the provided list), and the Japanese-only text might limit clarity for non-Japanese agents. It's specific enough to understand what it does but lacks differentiation context.

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. There are no explicit instructions about when this tool is appropriate, what prerequisites might exist, or how it differs from other list-retrieval tools like getIssues or getProjects. The agent must infer usage from the name and description alone without any contextual hints.

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

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