Skip to main content
Glama

linear_getIssueById

Retrieve a specific Linear issue using its ID or identifier to access project details and status information.

Instructions

Get a specific issue by ID or identifier (e.g., ABC-123)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID or identifier of the issue (e.g., ABC-123)

Implementation Reference

  • The main handler function for the linear_getIssueById tool. It validates the input arguments using isGetIssueByIdArgs and calls linearService.getIssueById(args.id) to fetch the issue.
     */
    export function handleGetIssueById(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isGetIssueByIdArgs(args)) {
            throw new Error('Invalid arguments for getIssueById');
          }
    
          return await linearService.getIssueById(args.id);
        } catch (error) {
          logError('Error getting issue by ID', error);
          throw error;
        }
      };
  • The MCPToolDefinition for linear_getIssueById, defining the tool's name, description, input schema (requires 'id' string), and detailed output schema.
    /**
     * Tool definition for getting issue by ID
     */
    export const getIssueByIdToolDefinition: MCPToolDefinition = {
      name: 'linear_getIssueById',
      description: 'Get a specific issue by ID or identifier (e.g., ABC-123)',
      input_schema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'The ID or identifier of the issue (e.g., ABC-123)',
          },
        },
        required: ['id'],
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          identifier: { type: 'string' },
          title: { type: 'string' },
          description: { type: 'string' },
          state: { type: 'string' },
          priority: { type: 'number' },
          estimate: { type: 'number' },
          dueDate: { type: 'string' },
          team: { type: 'object' },
          assignee: { type: 'object' },
          project: { type: 'object' },
          cycle: { type: 'object' },
          parent: { type: 'object' },
          labels: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                id: { type: 'string' },
                name: { type: 'string' },
                color: { type: 'string' },
              },
            },
          },
          sortOrder: { type: 'number' },
          createdAt: { type: 'string' },
          updatedAt: { type: 'string' },
          url: { type: 'string' },
          comments: { type: 'array' },
        },
      },
    };
  • Registration of the linear_getIssueById tool handler in the registerToolHandlers function, mapping the tool name to handleGetIssueById(linearService).
    linear_getIssueById: handleGetIssueById(linearService),
  • Type guard function isGetIssueByIdArgs used by the handler to validate input arguments for the linear_getIssueById tool.
     * Type guard for linear_getIssueById tool arguments
     */
    export function isGetIssueByIdArgs(args: unknown): args is { id: string } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'id' in args &&
        typeof (args as { id: string }).id === 'string'
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'Get[s] a specific issue', implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error handling (e.g., for invalid IDs), or response format. This is a significant gap for a tool with no annotation coverage.

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?

Single sentence, front-loaded with the core action, zero waste. It efficiently conveys the purpose without unnecessary details, making it easy to parse.

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 no annotations and no output schema, the description is incomplete. It lacks information on behavioral aspects (e.g., read-only nature, error cases) and return values, which are critical for a retrieval tool. The schema covers parameters well, but overall context is insufficient.

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%, with the parameter 'id' documented in the schema as 'The ID or identifier of the issue (e.g., ABC-123)'. The description adds minimal value beyond this, only restating 'by ID or identifier (e.g., ABC-123)'. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('a specific issue'), specifying it's by 'ID or identifier'. It distinguishes from siblings like linear_getIssues (list) and linear_searchIssues (search), though not explicitly named. However, it doesn't fully differentiate from linear_getIssueHistory, which might also retrieve an issue with additional data.

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 on when to use this tool versus alternatives like linear_getIssues (for listing) or linear_searchIssues (for filtering). It implies usage by ID but doesn't specify prerequisites (e.g., needing a valid issue ID) or exclusions (e.g., not for bulk retrieval).

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/tacticlaunch/mcp-linear'

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