Skip to main content
Glama
jootsuki

Backlog MCP Server

by jootsuki

searchIssues

Search Backlog issues by project, keywords, and status to find specific tasks or track progress in your workflow.

Instructions

Backlogの課題を検索します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesプロジェクトID(数値)
keywordNo検索キーワード
statusNoステータス(未対応、処理中、処理済み、完了)

Implementation Reference

  • MCP CallToolRequest handler specifically for 'searchIssues': validates input arguments using searchIssuesSchema and delegates execution to BacklogClient.searchIssues
    case 'searchIssues': {
      const args = this.validateAndCastArguments<SearchIssuesArgs>(
        request.params.arguments,
        searchIssuesSchema
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              await this.backlogClient.searchIssues(args),
              null,
              2
            ),
          },
        ],
      };
    }
  • Core handler function in BacklogClient that executes the searchIssues tool logic by calling Backlog API /issues endpoint
    async searchIssues(args: SearchIssuesArgs): Promise<BacklogIssue[]> {
      try {
        const response = await this.client.get('/issues', {
          params: {
            'projectId[]': [args.projectId],
            keyword: args.keyword,
            'statusId[]': args.status?.map(this.getStatusId),
          },
        });
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Backlog API error: ${error.response?.data.message ?? error.message}`);
        }
        throw error;
      }
    }
  • Input schema (JSON Schema) for the searchIssues tool defining parameters: projectId (required), keyword, status array
    export const searchIssuesSchema = {
      type: 'object',
      properties: {
        projectId: {
          type: 'number',
          description: 'プロジェクトID(数値)',
        },
        keyword: {
          type: 'string',
          description: '検索キーワード',
        },
        status: {
          type: 'array',
          items: {
            type: 'string',
          },
          description: 'ステータス(未対応、処理中、処理済み、完了)',
        },
      },
      required: ['projectId'],
    } as const;
  • src/index.ts:90-93 (registration)
    Registration of the searchIssues tool in the ListTools response, including name, description, and inputSchema reference
      name: 'searchIssues',
      description: 'Backlogの課題を検索します',
      inputSchema: searchIssuesSchema,
    },
  • TypeScript interface definition for SearchIssuesArgs used in handler validation and typing
    export interface SearchIssuesArgs {
      projectId: number;
      keyword?: string;
      status?: string[];
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, potential side effects, authentication requirements, rate limits, or response format. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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, front-loaded with the core action. It's appropriately sized for a basic tool, with no wasted words, though it could benefit from more detail given the lack of annotations and output schema.

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 complexity (search tool with 3 parameters), no annotations, and no output schema, the description is incomplete. It doesn't cover return values, error handling, or how search results are structured, leaving the agent with insufficient context for 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 input schema fully documents parameters (projectId, keyword, status). The description adds no meaning beyond the schema, as it doesn't explain parameter interactions, default behaviors, or search semantics. 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 'Backlogの課題を検索します' (Searches Backlog issues) states the basic action and resource (issues in Backlog), but it's vague about scope and doesn't distinguish from sibling tools like getIssue or updateIssue. It specifies the verb 'search' and target 'issues', but lacks detail on what 'search' entails versus 'get'.

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?

No guidance is provided on when to use this tool versus alternatives such as getIssue (which might retrieve a single issue) or updateIssue. The description implies searching multiple issues but doesn't clarify contexts like filtering needs or prerequisites, leaving the agent to infer usage from parameter 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/jootsuki/backlog-mcp-server'

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