Skip to main content
Glama
nulab

Backlog MCP Server

get_issues

Retrieve and filter project issues by criteria like status, priority, assignee, dates, and custom fields to track work items and manage project tasks.

Instructions

Returns list of issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject IDs
issueTypeIdNoIssue type IDs
categoryIdNoCategory IDs
versionIdNoVersion IDs
milestoneIdNoMilestone IDs
statusIdNoStatus IDs
priorityIdNoPriority IDs
assigneeIdNoAssignee user IDs
createdUserIdNoCreated user IDs
resolutionIdNoResolution IDs
parentIssueIdNoParent issue IDs
keywordNoKeyword to search for in issues
startDateSinceNoStart date since (yyyy-MM-dd)
startDateUntilNoStart date until (yyyy-MM-dd)
dueDateSinceNoDue date since (yyyy-MM-dd)
dueDateUntilNoDue date until (yyyy-MM-dd)
createdSinceNoCreated since (yyyy-MM-dd)
createdUntilNoCreated until (yyyy-MM-dd)
updatedSinceNoUpdated since (yyyy-MM-dd)
updatedUntilNoUpdated until (yyyy-MM-dd)
sortNoSort field
orderNoSort order
offsetNoOffset for pagination
countNoNumber of issues to retrieve
customFieldsNoCustom field filters (text, numeric, date, or list)

Implementation Reference

  • The async handler function that executes the get_issues tool logic by calling the Backlog API's getIssues method with processed parameters including custom fields.
    handler: async ({ customFields, ...rest }) => {
      return backlog.getIssues({
        ...rest,
        ...customFieldFiltersToPayload(customFields),
      });
    },
  • Zod schema definition for the input parameters of the get_issues tool, supporting filters by project, type, status, dates, custom fields, sorting, and pagination.
    const getIssuesSchema = buildToolSchema((t) => ({
      projectId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_PROJECT_ID', 'Project IDs')),
      issueTypeId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_ISSUE_TYPE_ID', 'Issue type IDs')),
      categoryId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_CATEGORY_ID', 'Category IDs')),
      versionId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_VERSION_ID', 'Version IDs')),
      milestoneId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_MILESTONE_ID', 'Milestone IDs')),
      statusId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_STATUS_ID', 'Status IDs')),
      priorityId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_PRIORITY_ID', 'Priority IDs')),
      assigneeId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_ASSIGNEE_ID', 'Assignee user IDs')),
      createdUserId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_CREATED_USER_ID', 'Created user IDs')),
      resolutionId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_RESOLUTION_ID', 'Resolution IDs')),
      parentIssueId: z
        .array(z.number())
        .optional()
        .describe(t('TOOL_GET_ISSUES_PARENT_ISSUE_ID', 'Parent issue IDs')),
      keyword: z
        .string()
        .optional()
        .describe(t('TOOL_GET_ISSUES_KEYWORD', 'Keyword to search for in issues')),
      startDateSince: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_ISSUES_START_DATE_SINCE', 'Start date since (yyyy-MM-dd)')
        ),
      startDateUntil: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_ISSUES_START_DATE_UNTIL', 'Start date until (yyyy-MM-dd)')
        ),
      dueDateSince: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_ISSUES_DUE_DATE_SINCE', 'Due date since (yyyy-MM-dd)')
        ),
      dueDateUntil: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_ISSUES_DUE_DATE_UNTIL', 'Due date until (yyyy-MM-dd)')
        ),
      createdSince: z
        .string()
        .optional()
        .describe(t('TOOL_GET_ISSUES_CREATED_SINCE', 'Created since (yyyy-MM-dd)')),
      createdUntil: z
        .string()
        .optional()
        .describe(t('TOOL_GET_ISSUES_CREATED_UNTIL', 'Created until (yyyy-MM-dd)')),
      updatedSince: z
        .string()
        .optional()
        .describe(t('TOOL_GET_ISSUES_UPDATED_SINCE', 'Updated since (yyyy-MM-dd)')),
      updatedUntil: z
        .string()
        .optional()
        .describe(t('TOOL_GET_ISSUES_UPDATED_UNTIL', 'Updated until (yyyy-MM-dd)')),
      sort: z
        .enum([
          'issueType',
          'category',
          'version',
          'milestone',
          'summary',
          'status',
          'priority',
          'attachment',
          'sharedFile',
          'created',
          'createdUser',
          'updated',
          'updatedUser',
          'assignee',
          'startDate',
          'dueDate',
          'estimatedHours',
          'actualHours',
          'childIssue',
        ])
        .optional()
        .describe(t('TOOL_GET_ISSUES_SORT', 'Sort field')),
      order: z
        .enum(['asc', 'desc'])
        .optional()
        .describe(t('TOOL_GET_ISSUES_ORDER', 'Sort order')),
      offset: z
        .number()
        .optional()
        .describe(t('TOOL_GET_ISSUES_OFFSET', 'Offset for pagination')),
      count: z
        .number()
        .optional()
        .describe(t('TOOL_GET_ISSUES_COUNT', 'Number of issues to retrieve')),
      customFields: z
        .array(buildCustomFieldFilterSchema(t))
        .optional()
        .describe(
          t(
            'TOOL_GET_ISSUES_CUSTOM_FIELDS',
            'Custom field filters (text, numeric, date, or list)'
          )
        ),
    }));
  • Import of the getIssuesTool factory function.
    import { getIssuesTool } from './getIssues.js';
  • Instantiation and registration of the get_issues tool in the 'issue' toolset group.
    getIssuesTool(backlog, helper),
  • Output schema for the get_issues tool using IssueSchema.
    outputSchema: IssueSchema,
Behavior1/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 but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether results are paginated (despite offset/count parameters), rate limits, or what the return format looks like. For a complex 25-parameter query tool, this represents a critical gap in understanding how the tool behaves.

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 extremely concise at just three words. While this represents severe under-specification for such a complex tool, from a pure conciseness perspective it's maximally efficient with zero wasted words. Every word ('Returns', 'list', 'issues') contributes directly to the core purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 25-parameter query tool with no annotations and no output schema, the three-word description is completely inadequate. It doesn't explain the extensive filtering capabilities, pagination behavior, return format, or how this differs from related tools. The description fails to provide the contextual information needed to effectively use this sophisticated query interface.

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 schema already documents all 25 parameters thoroughly with descriptions, formats, and enums. The description adds zero additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no parameter information in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Returns list of issues' is a tautology that essentially restates the tool name 'get_issues' with minimal additional information. It specifies the verb 'returns' and resource 'issues', but lacks any distinguishing details about scope, filtering capabilities, or how it differs from sibling tools like 'count_issues' or 'get_issue' (singular).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance on when to use this tool versus alternatives. With multiple sibling tools like 'count_issues' (for counting), 'get_issue' (for single issue retrieval), and 'get_issues' (for listing), the agent receives no indication about appropriate contexts, prerequisites, or trade-offs between these similar tools.

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