Skip to main content
Glama

Coline

List issues

list_upstream_issues
Read-onlyIdempotent

Lists a repository's issues on Upstream: open by default, filtered by label or assignee handle. Not Coline tasks.

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": {
      "workspace": "<workspace>",
      "repository": "<repository>"
    },
    "name": "list_upstream_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
stateNoopen
cursorNonextCursor from the previous page.
labelsNo
assigneeNoA handle, or "none" for unassigned issues.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
repositoryYesRepository name in this workspace, from list_repositories.

Output Schema

NameRequiredDescriptionDefault
issuesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds real behavioral context by stating the default state and that results can be filtered, but says nothing about pagination or result volume beyond what the cursor parameter already documents.

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, no filler, with the core purpose front-loaded and the disambiguating note trailing. Every clause carries information an agent needs.

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?

With an output schema present and rich annotations, the description need not explain return values or safety. For a 7-parameter filtered-list tool it covers purpose, default scope, and the main confusion risk; only pagination behavior is left implicit.

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 57%, with workspace, repository, cursor and assignee partially documented in-schema. The description reinforces the state default and clarifies that label and assignee are filters, but adds nothing about limit, cursor paging, or multi-label semantics, so it neither compensates for nor extends much beyond the schema.

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?

The description pairs a specific verb and resource ('Lists a repository's issues on Upstream') with the platform scope and a clarifying exclusion ('Not Coline tasks'), which separates it from the task-listing siblings. It stops short of naming a concrete sibling alternative such as get_upstream_issue for single-issue lookup.

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

Usage Guidelines4/5

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

It states a usage-relevant default ('open by default') and a when-not condition ('Not Coline tasks'), which keeps an agent from misrouting task queries here. It does not point to the tool to use for a single issue or for creating/updating issues.

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