Skip to main content
Glama

count_issues

Count issues in Backlog projects by filtering based on project, issue type, category, version, milestone, status, priority, assignee, keyword, and date ranges for effective issue tracking.

Instructions

Returns count of issues

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneeIdNoAssignee user IDs
categoryIdNoCategory IDs
createdSinceNoCreated since (yyyy-MM-dd)
createdUntilNoCreated until (yyyy-MM-dd)
createdUserIdNoCreated user IDs
dueDateSinceNoDue date since (yyyy-MM-dd)
dueDateUntilNoDue date until (yyyy-MM-dd)
issueTypeIdNoIssue type IDs
keywordNoKeyword to search for in issues
milestoneIdNoMilestone IDs
parentIssueIdNoParent issue IDs
priorityIdNoPriority IDs
projectIdNoProject IDs
resolutionIdNoResolution IDs
startDateSinceNoStart date since (yyyy-MM-dd)
startDateUntilNoStart date until (yyyy-MM-dd)
statusIdNoStatus IDs
updatedSinceNoUpdated since (yyyy-MM-dd)
updatedUntilNoUpdated until (yyyy-MM-dd)
versionIdNoVersion IDs

Implementation Reference

  • The handler function implementing the core logic of the 'count_issues' tool. It calls the Backlog API's getIssuesCount method with the input parameters and transforms custom fields.
    handler: async ({ customFields, ...rest }) => { return backlog.getIssuesCount({ ...rest, ...customFieldFiltersToPayload(customFields), }); },
  • Input schema definition for the 'count_issues' tool, defining optional array and string filters for querying issue counts.
    const countIssuesSchema = buildToolSchema((t) => ({ projectId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_PROJECT_ID', 'Project IDs')), issueTypeId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_ISSUE_TYPE_ID', 'Issue type IDs')), categoryId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_CATEGORY_ID', 'Category IDs')), versionId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_VERSION_ID', 'Version IDs')), milestoneId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_MILESTONE_ID', 'Milestone IDs')), statusId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_STATUS_ID', 'Status IDs')), priorityId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_PRIORITY_ID', 'Priority IDs')), assigneeId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_ASSIGNEE_ID', 'Assignee user IDs')), createdUserId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_CREATED_USER_ID', 'Created user IDs')), resolutionId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_RESOLUTION_ID', 'Resolution IDs')), parentIssueId: z .array(z.number()) .optional() .describe(t('TOOL_COUNT_ISSUES_PARENT_ISSUE_ID', 'Parent issue IDs')), keyword: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_KEYWORD', 'Keyword to search for in issues') ), startDateSince: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_START_DATE_SINCE', 'Start date since (yyyy-MM-dd)') ), startDateUntil: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_START_DATE_UNTIL', 'Start date until (yyyy-MM-dd)') ), dueDateSince: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_DUE_DATE_SINCE', 'Due date since (yyyy-MM-dd)') ), dueDateUntil: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_DUE_DATE_UNTIL', 'Due date until (yyyy-MM-dd)') ), createdSince: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_CREATED_SINCE', 'Created since (yyyy-MM-dd)') ), createdUntil: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_CREATED_UNTIL', 'Created until (yyyy-MM-dd)') ), updatedSince: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_UPDATED_SINCE', 'Updated since (yyyy-MM-dd)') ), updatedUntil: z .string() .optional() .describe( t('TOOL_COUNT_ISSUES_UPDATED_UNTIL', 'Updated until (yyyy-MM-dd)') ), customFields: z .array(buildCustomFieldFilterSchema(t)) .optional() .describe( t( 'TOOL_COUNT_ISSUES_CUSTOM_FIELDS', 'Custom field filters (text, numeric, date, or list)' ) ), }));
  • Tool schema configuration using the countIssuesSchema and output IssueCountSchema.
    schema: z.object(countIssuesSchema(t)), outputSchema: IssueCountSchema,
  • Registration of the 'count_issues' tool within the 'issue' toolset group in the allTools export.
    countIssuesTool(backlog, helper),

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