Skip to main content
Glama
Sign In
GitHub + Linear Dev Workflows

GitHub + Linear Dev Workflows

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

github_pulls_list

Read-onlyIdempotent

List pull requests and filter by state, base branch, or head user:branch to find relevant PRs for GitHub and Linear dev workflows.

Instructions

List pull requests. Filter by state, by base branch, or by head in the form 'user:branch'.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "github_pulls_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoFilter pulls by base branch name. Example: `gh-pages`.
headNoFilter pulls by head user or head organization and branch name in the format of `user:ref-name` or `organization:ref-name`.
pageNoThe page number of the results to fetch. Defaults to 1.
repoYesThe name of the repository without the `.git` extension. The name is not case sensitive.
sortNoWhat to sort results by. Defaults to `created`.created
ownerYesThe account owner of the repository. The name is not case sensitive.
stateNoEither `open`, `closed`, or `all` to filter by state. Defaults to `open`.open
perPageNoThe number of results per page (max 100). Defaults to 30.
directionNoThe direction of the sort. Default: `desc` when sort is `created` or not specified, otherwise `asc`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds only the filter hint and the 'user:branch' head form, without disclosing pagination behavior or result ordering beyond what annotations provide.

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 short sentences, front-loaded with the core action and then the filtering options. No filler or redundant phrasing.

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?

For a read-only list tool with full schema coverage, no output schema and complete annotations, the description is nearly sufficient. It omits mention of pagination and sort, but those are covered by the schema, so the gap is minor.

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 all nine parameters are already documented, including state, base, head, sort and pagination. The description essentially restates the filter semantics already in the schema, so baseline 3 applies.

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 ('List') and resource ('pull requests'), so the action is unambiguous. However, it doesn't differentiate from siblings like github_releases_generate_notes or explain its scope relative to any other PR tooling, since no close PR-list sibling exists.

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 mention of filters ('state', 'base', 'head') implies when the tool is useful, but there is no explicit when-to-use vs when-not guidance or named alternatives. Usage is left to inference.

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

Deploy Server

Other Tools