Skip to main content
Glama
tacticlaunch

Linear

by tacticlaunch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

linear_searchIssues

Read-onlyIdempotent

Search issues with filters for text, state, team, project, assignee, and dates to find specific work items.

Instructions

Search for issues with various filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datesNoDate filters. Each key takes { after, before, on }; all provided filters must match
limitNoMaximum number of issues to return (default: 10)
queryNoText to search for in issue title or description
statesNoFilter issues by state name (e.g., 'Todo', 'In Progress', 'Done')
teamIdNoFilter issues by team ID
projectIdNoFilter issues by project ID
assigneeIdNoFilter issues by assignee ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.5
    • addedInput schema / properties / dates
      Added value: +{
+  "additionalProperties": false,
+  "description": "Date filters. Each key takes { after, before, on }; all provided filters must match",
+  "properties": {
+    "autoClosed": {
+      "additionalProperties": false,
+      "description": "Filter by auto-close date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "completed": {
+      "additionalProperties": false,
+      "description": "Filter by completion date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "created": {
+      "additionalProperties": false,
+      "description": "Filter by creation date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "due": {
+      "additionalProperties": false,
+      "description": "Filter by due date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date or an ISO 8601 duration relative to today (e.g., 'P1W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date or an ISO 8601 duration relative to today (e.g., 'P1W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "started": {
+      "additionalProperties": false,
+      "description": "Filter by start date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "triaged": {
+      "additionalProperties": false,
+      "description": "Filter by triage date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "updated": {
+      "additionalProperties": false,
+      "description": "Filter by last update date. 'after' is inclusive and 'before' is exclusive; 'on' cannot be combined with 'after' or 'before'",
+      "properties": {
+        "after": {
+          "description": "On or after (inclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "before": {
+          "description": "Before (exclusive): a YYYY-MM-DD date (whole UTC day), an ISO 8601 date-time (e.g., '2026-10-01T15:00:00Z'), or an ISO 8601 duration relative to now (e.g., '-P2W')",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "on": {
+          "description": "On this calendar day (YYYY-MM-DD, UTC)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed13 schema fields changedv1.4.2
    • changedOutput schema / properties / items / items / properties / assignee / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / cycle / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / description / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / dueDate / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / estimate / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / labels / items / properties / color / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / parent / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / priority / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / project / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / projectMilestone / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / sortOrder / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / state / properties / color / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / items / items / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  3. Changed1 schema field changedv1.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "assignee": {
+            "type": "object"
+          },
+          "createdAt": {
+            "type": "string"
+          },
+          "cycle": {
+            "type": "object"
+          },
+          "description": {
+            "type": "string"
+          },
+          "dueDate": {
+            "type": "string"
+          },
+          "estimate": {
+            "type": "number"
+          },
+          "id": {
+            "type": "string"
+          },
+          "identifier": {
+            "type": "string"
+          },
+          "labels": {
+            "items": {
+              "properties": {
+                "color": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "parent": {
+            "type": "object"
+          },
+          "priority": {
+            "type": "number"
+          },
+          "project": {
+            "type": "object"
+          },
+          "projectMilestone": {
+            "type": "object"
+          },
+          "sortOrder": {
+            "type": "number"
+          },
+          "state": {
+            "properties": {
+              "color": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "team": {
+            "type": "object"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, covering the safety and idempotency profile. The description adds nothing beyond that – it doesn't mention pagination via limit, result ordering, or whether filters are ANDed together (though the schema's 'dates' description hints at AND semantics for that object). For a search tool with zero annotation gaps to fill, the description under-delivers on behavioral context.

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

Conciseness3/5

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

At seven words it is certainly concise, but it is under-specified rather than efficiently structured – there is no front-loaded scoping information beyond the bare verb+resource. Brevity here comes at the cost of usefulness, which is a structural gap rather than a virtue.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But with 7 parameters, nested date objects, and a rich set of sibling issue tools, a one-phrase description is inadequate: it does not say whether filters are conjunctive, whether results are paginated beyond limit, or how it differs from getIssues. The schema covers parameters, but the description fails to orient the agent on when and why to call this tool.

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% and the nested schemas are richly documented (date semantics, limit default, query target, state examples). The description adds no parameter detail beyond 'various filters'. Per the rubric, when schema coverage is high, baseline 3 is appropriate even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (search) and resource (issues) with filters, which is clear enough on its own. However, it does not distinguish this from sibling tools like linear_getIssues or linear_getProjectIssues, which are also issue-listing tools. An agent cannot tell from the description alone when to prefer searchIssues over getIssues.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives, and no exclusion criteria. The agent is left to infer that 'various filters' is the distinguishing factor, but with no comparison to getIssues or searchDocuments, this is effectively no guidance.

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