Linear

linear_getProjectIssues

Read-onlyIdempotent

Fetch a project's issues, filtering by workflow state, assignee, labels, cycle, or milestone for targeted insights.

Instructions

Get issues associated with a project, with PM-friendly filters like state, assignee, labels, cycle, and milestone

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of issues to return (default: 25)
`states`	No	Filter issues by workflow state names
`cycleId`	No	Filter issues by cycle ID
`orderBy`	No	Sort issues by created or updated date
`labelIds`	No	Filter issues by label IDs
`projectId`	Yes	ID of the project to get issues for
`assigneeId`	No	Filter issues by assignee ID
`includeCompleted`	No	Include completed issues in the result set (default: true)
`projectMilestoneId`	No	Filter issues by project milestone ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedv1.4.2Aug 27, 2026
- changedOutput schema / properties / items / items / properties / labels / items / properties / color / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / priority / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / sortOrder / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedv1.4.1Jul 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "assignee": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "cycle": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "description": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "dueDate": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "estimate": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "identifier": {
+            "type": "string"
+          },
+          "labels": {
+            "items": {
+              "properties": {
+                "color": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "priority": {
+            "type": "number"
+          },
+          "projectMilestone": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "sortOrder": {
+            "type": "number"
+          },
+          "state": {
+            "properties": {
+              "color": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "type": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "team": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Changed9 schema fields changedv1.1.2May 4, 2026

addedInput schema / properties / assigneeId

Added value: +{
+  "description": "Filter issues by assignee ID",
+  "type": "string"
+}

addedInput schema / properties / cycleId

Added value: +{
+  "description": "Filter issues by cycle ID",
+  "type": "string"
+}

addedInput schema / properties / includeCompleted

Added value: +{
+  "description": "Include completed issues in the result set (default: true)",
+  "type": "boolean"
+}

addedInput schema / properties / labelIds

Added value: +{
+  "description": "Filter issues by label IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

addedInput schema / properties / orderBy

Added value: +{
+  "description": "Sort issues by created or updated date",
+  "enum": [
+    "createdAt",
+    "updatedAt"
+  ],
+  "type": "string"
+}

addedInput schema / properties / projectMilestoneId

Added value: +{
+  "description": "Filter issues by project milestone ID",
+  "type": "string"
+}

addedInput schema / properties / states

Added value: +{
+  "description": "Filter issues by workflow state names",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedAug 18, 2025

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already disclose readOnly, idempotent, and non-destructive behavior, so the description does not need to repeat them. It adds no extra behavioral detail (e.g., pagination behavior or default includeCompleted), but remains consistent with annotations and provides a modest amount of context about filter capabilities.

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?

The description is a single sentence, front-loads the primary action ('Get issues associated with a project'), and contains no superfluous wording. It is efficient and well structured.

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 tool with 9 parameters, a 100% schema coverage, an output schema, and annotations covering safety, the description covers the core purpose and filter categories. It omits explicit mention of defaults (limit, includeCompleted) and ordering, but those are documented in the schema. The only notable gap is explicit usage differentiation from sibling issue-retrieval tools, which is addressed under usage guidelines.

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% — every parameter has a description. The description's mention of 'state, assignee, labels, cycle, and milestone' loosely maps to states, assigneeId, labelIds, cycleId, projectMilestoneId, but does not add syntax or semantics beyond what the schema already provides. Baseline 3 applies for high schema coverage.

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 uses a specific verb ('Get'), a clear resource ('issues'), and a scoping noun ('project'), and enumerates filter dimensions (state, assignee, labels, cycle, milestone). It implies distinction from siblings like linear_getIssues by tying results to a project, but does not explicitly name an alternative.

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 implies the tool is for project-scoped issue retrieval and lists filter categories, giving an agent an idea of supported queries. However, it does not state when to prefer this over linear_getIssues or linear_searchIssues, nor does it mention the required projectId or any exclusions.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/tacticlaunch/mcp-linear'

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