Skip to main content
Glama

linear_createProject

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

Instructions

Create a new project in Linear

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the project
descriptionNoShort summary of the project
contentNoContent 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 main handler function for the linear_createProject tool. It validates the input arguments using a type guard and delegates to LinearService.createProject.
    /**
     * Handler for creating a project
     */
    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;
        }
      };
  • MCP tool definition for linear_createProject, including detailed input and output schemas.
    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: 'Short summary of the project',
          },
          content: {
            type: 'string',
            description: 'Content 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' },
        },
      },
    };
  • Registration of the linear_createProject tool handler within the registerToolHandlers function.
    linear_getProjects: handleGetProjects(linearService),
    linear_createProject: handleCreateProject(linearService),
  • Type guard function used by the handler to validate input arguments for linear_createProject.
     * Type guard for linear_createProject tool arguments
     */
    export function isCreateProjectArgs(args: unknown): args is {
      name: string;
      description?: string;
      content?: 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?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention required permissions, whether this operation is idempotent, what happens on failure, or what the response contains. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 unnecessary words. It's appropriately sized for a creation tool and front-loads the essential information. Every word earns its place.

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 mutation tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation, what permissions are needed, how to handle errors, or provide any context about the Linear project system. The description alone doesn't give an agent enough information to use this tool confidently.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema descriptions. This meets the baseline expectation when schema does the heavy lifting, but provides no extra value.

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 action ('Create') and resource ('new project in Linear'), making the purpose immediately understandable. It distinguishes this from sibling tools like linear_createIssue or linear_createInitiative by specifying the project resource type. However, it doesn't explicitly differentiate scope or constraints beyond the basic verb+resource pairing.

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. With sibling tools like linear_createIssue and linear_createInitiative available, there's no indication of when project creation is appropriate versus issue or initiative creation. No prerequisites, constraints, or comparative context is mentioned.

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

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