Retrieve all projects from your Linear workspace to view ongoing work and statuses.
Get a list of projects from Linear
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.4.1Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "items": {
+ "items": {
+ "properties": {
+ "color": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "content": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "icon": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "type": "string"
+ },
+ "lead": {
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "microsoftTeamsChannelId": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "type": "string"
+ },
+ "slackChannelId": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "startDate": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "state": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "targetDate": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "teams": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "trashed": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "items"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds no extra behavioral context (e.g., whether results are paginated or ordered), but does not contradict annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that is perfectly concise and front-loaded. Every word earns its place; no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, annotations covering safety, and an output schema (exists but not shown), the description is complete enough. It tells the agent exactly what the tool does without missing context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so the schema coverage is 100%. Following guidelines, zero parameters baseline is 4. The description adds no parameter info, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Get a list of projects from Linear' clearly states the verb (get) and resource (list of projects). It distinguishes from siblings like linear_getProjectById (single project) and linear_createProject (create), making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives (e.g., linear_getProjectById for a specific project). For a zero-param list tool, usage is somewhat implied, but no exclusions or context are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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