Skip to main content
Glama
tmhr1850

Backlog MCP Server

getProjects

Retrieve project listings from Backlog to manage tasks and track issues through the MCP server interface.

Instructions

プロジェクト一覧の取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the getProjects tool (shared with other tools). It parses input with the tool's Zod schema, prepares the endpoint path 'projects', calls fetchFromBacklog, and returns the JSON stringified data.
    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,
        };
      }
    };
  • The MCP server.tool() registration that binds the name 'getProjects', description, and generic handler function for execution.
    server.tool(
      endpoint.name,
      endpoint.description,
      async (args: Record<string, unknown>) => handler(args)
    );
  • src/endpoints.ts:21-28 (registration)
    The BacklogEndpoint configuration object for 'getProjects', specifying name, description, API path ('projects'), method ('GET'), input schema (empty object), and type ('tool'). Serves as both registration data and schema definition.
    {
      name: "getProjects",
      description: "プロジェクト一覧の取得",
      path: "projects",
      method: "GET",
      schema: z.object({}).strict(),
      type: "tool"
    },
  • The fetchFromBacklog utility function that performs the actual API call to https://{domain}/api/v2/projects for getProjects, managing URL construction, query/body params, authentication via apiKey, error handling, and JSON response processing.
    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 registerEndpoints(server), which iterates over endpoints and registers the getProjects tool among others.
    registerEndpoints(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '取得' (get) implies a read operation, it doesn't specify whether this is paginated, filtered, sorted, or what permissions are required. No rate limits, authentication needs, or response format details are mentioned, leaving significant behavioral gaps.

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 phrase that directly states the tool's purpose without any wasted words. It's appropriately sized for a simple list tool and front-loads the essential information immediately.

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 list retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the projects are returned in, whether there's pagination, what fields are included, or any error conditions. The context signals show this is a simple tool, but even simple tools need basic behavioral context that's missing here.

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, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps, and it correctly implies this is a simple list operation without filtering parameters. Baseline for 0 parameters with full schema coverage is 4.

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 'プロジェクト一覧の取得' (Get project list) clearly states the verb ('取得' - get) and resource ('プロジェクト一覧' - project list), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'getSpaces' or 'getUsers', but the resource specificity is clear enough for basic understanding.

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 like 'getIssues' or 'getSpaces'. There's no mention of prerequisites, context, or comparison with sibling tools, leaving the agent to infer usage based on tool names 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

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