Skip to main content
Glama

get_issue

Retrieve details about a specific issue from Backlog project management using either its numeric ID or issue key to access project information.

Instructions

Returns information about a specific issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdNoThe numeric ID of the issue (e.g., 12345)
issueKeyNoThe key of the issue (e.g., 'PROJ-123')

Implementation Reference

  • The async handler function that resolves the issue identifier (ID or key) and retrieves the issue details using the Backlog client.
    handler: async ({ issueId, issueKey }) => { const result = resolveIdOrKey('issue', { id: issueId, key: issueKey }, t); if (!result.ok) { throw result.error; } return backlog.getIssue(result.value); },
  • Zod input schema for the get_issue tool, defining optional issueId (number) or issueKey (string) parameters.
    const getIssueSchema = buildToolSchema((t) => ({ issueId: z .number() .optional() .describe( t('TOOL_GET_ISSUE_ISSUE_ID', 'The numeric ID of the issue (e.g., 12345)') ), issueKey: z .string() .optional() .describe( t('TOOL_GET_ISSUE_ISSUE_KEY', "The key of the issue (e.g., 'PROJ-123')") ), }));
  • Instantiation and registration of the get_issue tool within the 'issue' toolset group.
    getIssueTool(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