Skip to main content
Glama

backport_pr

Destructive

Backport a merged pull request onto another branch by asking Aviator to open a new PR with the required changes.

Instructions

Ask Aviator to backport a merged PR onto another branch (it opens a new PR).

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": {
      "number": "<number>",
      "target_branch": "<target_branch>"
    },
    "name": "backport_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoGitHub org. Optional if repo is 'org/name'.
repoNoGitHub repo name or 'org/name'.
numberYesPull request number.
target_branchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false; the description usefully adds the concrete effect that a new PR is opened rather than the branch being modified in place. It does not mention permissions, auth, or failure modes, which keeps it from a 5.

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?

A single sentence with the action front-loaded and the side effect in a parenthetical. 'Ask Aviator to' is slightly redundant phrasing but no substantive waste.

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

Completeness3/5

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

For a 4-parameter mutation with annotations and no output schema, the description covers the essential outcome (new PR created on the target branch). It omits what happens on failure, whether the target branch must already exist, and any permissions needed.

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 75% and only target_branch lacks its own description; the phrase 'onto another branch' supplies that meaning. The description adds nothing about number, org, or repo beyond what the schema already documents, so it sits at the baseline.

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?

States a specific verb ('backport') and resource ('a merged PR') plus the target ('another branch'), which is enough to separate it from queue_pr or dequeue_pr. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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 phrase 'a merged PR' implicitly tells the agent the precondition (the PR must already be merged) and that the result lands on a different branch. There is no explicit statement of when to prefer this over other PR tools or what to do for unmerged PRs.

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