Skip to main content
Glama

task_link_github

Idempotent

Link a pull request, issue or commit from the project's connected GitHub repository to a task. Link the PR you opened for a task: it then shows on the task, and merging it into the default branch closes the task. A PR whose branch is named fb- (like fb-12-fix-header) or whose description says "Fixes FB-" links itself, so this is for PRs that don't. Linking the same URL twice does nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "taskId": "<taskId>",
      "url": "<url>",
      "context": "<context>"
    },
    "name": "task_link_github"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe GitHub URL, like https://github.com/owner/repo/pull/12
taskIdYesThe task ID or number (FB-360 or 360)
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
projectIdYesThe project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing downstream effects that structured hints cannot express: the link surfaces on the task and merging the PR into the default branch closes the task. It also restates idempotency concretely ("Linking the same URL twice does nothing"), reinforcing idempotentHint=true, and requires the target be a connected GitHub repository.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the action in the first sentence, then the primary scenario, then the auto-link exclusion and idempotency note. Every sentence contributes, though the branch-naming aside is slightly dense relative to the rest.

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?

Covers purpose, triggering conditions, side effects and duplicate handling for a four-parameter mutation with an open-world hint. It does not explain what happens when linking an issue or commit (only PR consequences are described) or any permission/connected-repo prerequisites, which leaves a small gap.

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 coverage is 100%, so url format, taskId (FB-360 or 360), projectId and the context-parameter requirements are already fully documented in the schema. The description adds nothing further about parameters, leaving it at the baseline for a fully-documented schema.

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?

States a specific verb (link) plus resource (GitHub PR/issue/commit) and the exact destination (a task) within a scoped repository. It also disambiguates from the automatic branch/commit-message linking path, so an agent can tell which mechanism it is invoking without consulting siblings.

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

Usage Guidelines5/5

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

Explicitly names both the use case ("Link the PR you opened for a task") and the exclusion ("this is for PRs that don't" auto-link), including the exact auto-link conventions (fb-<number> branch or "Fixes FB-<number>") so the agent can decide before calling. It also states the no-op case for duplicate URLs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources