Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_createProject

Create a new project in Linear with name, description, team assignments, and initial status to organize work and track progress.

Instructions

Create a new project in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the project
descriptionNoDescription of the project (Markdown supported)
teamIdsYesIDs of the teams this project belongs to
stateNoInitial state of the project (e.g., 'planned', 'started', 'paused', 'completed', 'canceled')

Implementation Reference

  • The handler function that executes the linear_createProject tool logic. Validates input args and delegates to LinearService.createProject.
    export function handleCreateProject(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          if (!isCreateProjectArgs(args)) {
            throw new Error("Invalid arguments for createProject");
          }
          
          return await linearService.createProject(args);
        } catch (error) {
          logError("Error creating project", error);
          throw error;
        }
      };
    }
  • Input/output schema definition for the linear_createProject tool.
    export const createProjectToolDefinition: MCPToolDefinition = {
      name: "linear_createProject",
      description: "Create a new project in Linear",
      input_schema: {
        type: "object",
        properties: {
          name: {
            type: "string",
            description: "Name of the project",
          },
          description: {
            type: "string",
            description: "Description of the project (Markdown supported)",
          },
          teamIds: {
            type: "array",
            items: { type: "string" },
            description: "IDs of the teams this project belongs to",
          },
          state: {
            type: "string",
            description: "Initial state of the project (e.g., 'planned', 'started', 'paused', 'completed', 'canceled')",
          },
        },
        required: ["name", "teamIds"],
      },
      output_schema: {
        type: "object",
        properties: {
          id: { type: "string" },
          name: { type: "string" },
          url: { type: "string" }
        }
      }
    };
  • Maps the tool name 'linear_createProject' to its handler function in the registerToolHandlers export.
    linear_createProject: handleCreateProject(linearService),
  • Type guard helper 'isCreateProjectArgs' for validating tool input arguments.
     * Type guard for linear_createProject tool arguments
     */
    export function isCreateProjectArgs(args: unknown): args is {
      name: string;
      description?: string;
      teamIds: string[];
      state?: string;
    } {
      return (
        typeof args === "object" &&
        args !== null &&
        "name" in args &&
        typeof (args as { name: string }).name === "string" &&
        "teamIds" in args &&
        Array.isArray((args as { teamIds: string[] }).teamIds)
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Create' implies a write/mutation operation, the description doesn't mention required permissions, whether this is an idempotent operation, what happens on duplicate names, or what the response contains. For a creation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a straightforward creation tool and gets directly to the point.

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?

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation, what the return value contains, or address common behavioral questions like permissions, idempotency, or error conditions. The 100% schema coverage helps with parameters, but overall context is lacking.

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 description coverage is 100%, so the schema already documents all 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. This meets the baseline expectation when schema coverage is complete.

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 clearly states the verb ('Create') and resource ('new project in Linear'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like linear_updateProject or linear_getProjects, but the creation action is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when creation is appropriate versus updating existing projects, or how this relates to sibling tools like linear_updateProject or linear_getProjects.

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

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

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