Skip to main content
Glama
tmhr1850

Backlog MCP Server

getIssue

Retrieve specific issue details from Backlog project management system to track progress and access task information.

Instructions

特定の課題情報の取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Shared handler function that executes the 'getIssue' tool logic: validates input parameters using the endpoint's Zod schema, processes URI and path templates (e.g., substitutes {issueId} in 'issues/{issueId}'), calls fetchFromBacklog to retrieve issue data from Backlog API, and returns formatted JSON response or error message.
    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,
        };
      }
    };
  • Configuration and input schema for the 'getIssue' tool: requires 'issueId' parameter (string or positive number), maps to Backlog API path 'issues/{issueId}' via GET request.
    {
      name: "getIssue",
      description: "特定の課題情報の取得",
      path: "issues/{issueId}",
      method: "GET",
      schema: z.object({ issueId: issueIdSchema }),
      type: "tool",
    },
  • Registers the 'getIssue' tool (and other tools) with the MCP server using server.tool(), providing the name, description from config, and the shared handler function.
    if (endpoint.type === "tool") {
      // ツールの登録
      server.tool(
        endpoint.name,
        endpoint.description,
        async (args: Record<string, unknown>) => handler(args)
      );
  • Helper function called by the handler to perform the actual HTTP request to Backlog API: handles authentication, query/body params (including arrays), path processing, comprehensive error handling for network, HTTP, and Backlog-specific errors.
    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 that triggers registration of all endpoints including the 'getIssue' tool.
    registerEndpoints(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it retrieves information, implying a read-only operation, but doesn't cover aspects like authentication needs, error handling, rate limits, or what constitutes 'specific' (e.g., by ID). It lacks behavioral details beyond the basic purpose.

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 a single, efficient sentence in Japanese that directly states the purpose without waste. It's appropriately sized for a simple tool, though it could be more structured if it included usage notes. No fluff or redundancy is present.

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, no annotations), the description is minimal but incomplete. It doesn't explain what 'specific' means, how to identify issues, or what information is returned, leaving gaps for the agent. For a retrieval tool with no structured guidance, it should provide more context.

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 input schema has 0 parameters with 100% description coverage, so no parameters need documentation. The description doesn't add parameter details, but with no parameters, the baseline is 4 as it doesn't need to compensate for gaps. It's adequate given the schema's completeness.

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 '特定の課題情報の取得' (retrieves specific issue information) states a clear verb ('取得' - retrieve) and resource ('課題情報' - issue information), but it's vague about what makes an issue 'specific' and doesn't differentiate from sibling tools like 'getIssues' which likely retrieves multiple issues. It's not tautological with the name 'getIssue' but lacks specificity.

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 prerequisites, context for 'specific' issues, or how it differs from 'getIssues' (e.g., single vs. multiple issues). Without any usage context, the agent must infer from the name 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