Skip to main content
Glama

track

Monitor GitHub pull requests by adding them to your tracking list for daily status checks and automated reports.

Instructions

Start tracking a pull request. Adds the PR to your monitored list so it appears in daily checks and status reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prUrlYesFull GitHub PR URL to track (e.g. https://github.com/owner/repo/pull/123)

Implementation Reference

  • The actual implementation of the "track" tool, which validates the provided PR URL and fetches metadata from GitHub.
    export async function runTrack(options: { prUrl: string }): Promise<TrackOutput> {
      validateUrl(options.prUrl);
      validateGitHubUrl(options.prUrl, PR_URL_PATTERN, 'PR');
    
      const token = requireGitHubToken();
      const octokit = getOctokit(token);
    
      const parsed = parseGitHubUrl(options.prUrl);
      if (!parsed || parsed.type !== 'pull') {
        throw new Error(`Invalid PR URL: ${options.prUrl}`);
      }
    
      const { owner, repo, number } = parsed;
    
      const { data: ghPR } = await octokit.pulls.get({ owner, repo, pull_number: number });
    
      return {
        pr: {
          repo: `${owner}/${repo}`,
          number,
          title: ghPR.title,
          url: options.prUrl,
        },
      };
    }
  • Registration of the "track" tool in the MCP server, binding it to the `runTrack` handler.
    // 5. track — Track a PR
    server.registerTool(
      'track',
      {
        description:
          'Start tracking a pull request. Adds the PR to your monitored list so it appears in daily checks and status reports.',
        inputSchema: {
          prUrl: z.string().describe('Full GitHub PR URL to track (e.g. https://github.com/owner/repo/pull/123)'),
        },
        annotations: { readOnlyHint: false, destructiveHint: false },
      },
      wrapTool(runTrack),
    );
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds valuable behavioral context by disclosing the side effects: the PR gets added to a monitored list and will appear in daily checks and status reports, explaining integration with the broader system.

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?

Two well-structured sentences with zero waste. The first sentence front-loads the action ('Start tracking'), and the second explains the system effect. Every sentence earns its place without redundancy.

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 low complexity (single required parameter, no output schema, clear annotations), the description successfully explains the system's behavioral integration (daily checks, status reports) which is the primary value of this tool. No significant gaps remain.

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?

With 100% schema description coverage, the input schema fully documents the 'prUrl' parameter format and example. The description does not need to compensate for schema gaps, meeting the baseline expectation for well-documented parameters.

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 uses specific verb 'Start tracking' with resource 'pull request' and clarifies the scope by explaining it adds to a 'monitored list' for 'daily checks and status reports.' This clearly distinguishes it from sibling 'untrack' and read-only tools like 'status' or 'read'.

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?

The description explains the outcome (appears in daily checks and status reports) which implies when to use it, but provides no explicit when-to-use guidance, prerequisites, or named alternatives such as when to choose 'untrack' instead.

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/costajohnt/oss-autopilot'

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