Skip to main content
Glama
skippr-hq

Skippr Extension MCP Server

by skippr-hq

Get Skippr Issue Details

skippr_get_issue

Retrieves full details and raw markdown content for a specific Skippr issue. Enables AI agents to access issue data for fixing product problems.

Instructions

Gets full details for a specific Skippr issue including raw markdown content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject identifier
reviewIdYesReview ID
issueIdYesIssue ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
reviewIdYes
titleYes
severityYes
resolvedYes
categoryNo
markdownYes

Implementation Reference

  • Main handler function for the skippr_get_issue tool. Validates input (projectId, reviewId, issueId), reads the issue markdown file from .skippr/projects/{projectId}/reviews/{reviewId}/issues/{issueId}.md, parses frontmatter, and returns full issue details including raw markdown content.
    export async function getIssue(input: GetIssueInput): Promise<GetIssueOutput> {
      // Validate input
      const validated = GetIssueInputSchema.parse(input);
      const { projectId, reviewId, issueId } = validated;
    
      // Read and parse the issue file
      const { frontmatter, markdown } = await readIssueFile(projectId, reviewId, issueId);
    
      return {
        id: frontmatter.id,
        reviewId: frontmatter.reviewId,
        title: frontmatter.title,
        severity: frontmatter.severity,
        resolved: frontmatter.resolved,
        category: frontmatter.category,
        elementMetadata: frontmatter.elementMetadata,
        markdown, // Raw markdown for Claude to read
      };
    }
  • Input schema for skippr_get_issue, requiring projectId (string), reviewId (UUID), and issueId (UUID).
    export const GetIssueInputSchema = z.object({
      projectId: z.string().describe('Project identifier'),
      reviewId: z.string().uuid().describe('Review ID'),
      issueId: z.string().uuid().describe('Issue ID'),
    });
  • Output schema for skippr_get_issue, defining the returned issue details including id, reviewId, title, severity, resolved status, optional category and elementMetadata, plus raw markdown content.
    export const GetIssueOutputSchema = z.object({
      id: z.string().uuid(),
      reviewId: z.string().uuid(),
      title: z.string(),
      severity: z.string(),
      resolved: z.boolean(),
      category: z.string().optional(),
      elementMetadata: z
        .object({
          selector: z.string(),
          bounding_box: z.array(z.number()).optional(),
        })
        .optional(),
      markdown: z.string().describe('Raw markdown content for Claude to read'),
    });
  • Registration of the skippr_get_issue tool in the MCP server using mcpServer.registerTool(). Maps to the getIssue handler and passes its input/output schemas.
    mcpServer.registerTool(
      'skippr_get_issue',
      {
        title: 'Get Skippr Issue Details',
        description: 'Gets full details for a specific Skippr issue including raw markdown content',
        inputSchema: GetIssueInputSchema.shape,
        outputSchema: z.object({
          id: z.string(),
          reviewId: z.string(),
          title: z.string(),
          severity: z.string(),
          resolved: z.boolean(),
          category: z.string().optional(),
          markdown: z.string()
        }).shape
      },
      async (args) => {
        const result = await getIssue(args as GetIssueInput);
        return createStructuredResponse(result);
      }
    );
  • Helper that reads the issue markdown file from the filesystem at .skippr/projects/{projectId}/reviews/{reviewId}/issues/{issueId}.md and returns parsed frontmatter plus raw markdown.
    export async function readIssueFile(
      projectId: string,
      reviewId: string,
      issueId: string
    ): Promise<{ frontmatter: ParsedIssueFrontmatter; markdown: string }> {
      const filePath = join(getWorkingDirectory(), '.skippr', 'projects', projectId, 'reviews', reviewId, 'issues', `${issueId}.md`);
    
      const content = await readFile(filePath, 'utf-8');
      const parsed = parseIssueFrontmatter(content);
    
      return {
        frontmatter: parsed.frontmatter,
        markdown: parsed.content, // Raw markdown for Claude to read
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the output includes raw markdown, but does not mention side effects, permissions, or idempotency. The word 'Gets' implies a read operation, but more detail would be beneficial.

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 a single sentence that conveys the purpose concisely without unnecessary words. It is front-loaded and efficient.

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

Completeness4/5

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

Given the presence of an output schema and the simple nature of a get operation, the description is largely complete. It could be improved by briefly contrasting with skippr_list_issues or skippr_verify_issue_fix.

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 clear descriptions for each parameter. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb (Gets) and resource (full details for a specific Skippr issue) and distinguishes from siblings like skippr_list_issues by mentioning 'specific' and including 'raw markdown content'.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for retrieving a single issue, but does not mention alternatives or exclusions.

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/skippr-hq/extension-mcp-server'

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