Skip to main content
Glama

linear_createInitiative

Create a new initiative in Linear to organize and track strategic projects with details like name, description, owner, target date, and status.

Instructions

Create a new initiative

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the initiative
descriptionNoDescription of the initiative
contentNoContent in markdown format
ownerIdNoID of the user who owns the initiative
targetDateNoTarget completion date (ISO 8601 format)
statusNoStatus of the initiative
iconNoIcon emoji for the initiative
colorNoColor of the initiative in hex format

Implementation Reference

  • Core handler function for the 'linear_createInitiative' tool. Validates input with type guard and calls LinearService.createInitiative to perform the creation.
    export function createInitiativeHandler(linearService: LinearService) {
      return async (args: unknown) => {
        if (!isCreateInitiativeInput(args)) {
          throw new Error('Invalid input for createInitiative');
        }
    
        console.log('[createInitiative] Creating new initiative:', args.name);
        const result = await linearService.createInitiative(args);
        console.log(`[createInitiative] Initiative created successfully`);
        return result;
      };
    }
  • Tool definition including input and output schemas for 'linear_createInitiative'.
    {
      name: 'linear_createInitiative',
      description: 'Create a new initiative',
      input_schema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the initiative',
          },
          description: {
            type: 'string',
            description: 'Description of the initiative',
          },
          content: {
            type: 'string',
            description: 'Content in markdown format',
          },
          ownerId: {
            type: 'string',
            description: 'ID of the user who owns the initiative',
          },
          targetDate: {
            type: 'string',
            description: 'Target completion date (ISO 8601 format)',
          },
          status: {
            type: 'string',
            description: 'Status of the initiative',
            enum: ['notStarted', 'inProgress', 'completed', 'paused'],
          },
          icon: {
            type: 'string',
            description: 'Icon emoji for the initiative',
          },
          color: {
            type: 'string',
            description: 'Color of the initiative in hex format',
          },
        },
        required: ['name'],
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          name: { type: 'string' },
          description: { type: 'string' },
          status: { type: 'string' },
          url: { type: 'string' },
        },
      },
    },
  • Registration of the linear_createInitiative handler in the tool handlers map within registerToolHandlers function.
    linear_createInitiative: createInitiativeHandler(linearService),
  • Type guard function isCreateInitiativeInput used by the handler to validate input arguments.
     * Type guard for linear_createInitiative tool arguments
     */
    export function isCreateInitiativeInput(args: unknown): args is {
      name: string;
      description?: string;
      content?: string;
      ownerId?: string;
      targetDate?: string;
      status?: string;
      icon?: string;
      color?: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'name' in args &&
        typeof (args as { name: string }).name === 'string' &&
        (!('description' in args) ||
          typeof (args as { description: string }).description === 'string') &&
        (!('content' in args) || typeof (args as { content: string }).content === 'string') &&
        (!('ownerId' in args) || typeof (args as { ownerId: string }).ownerId === 'string') &&
        (!('targetDate' in args) || typeof (args as { targetDate: string }).targetDate === 'string') &&
        (!('status' in args) || typeof (args as { status: string }).status === 'string') &&
        (!('icon' in args) || typeof (args as { icon: string }).icon === 'string') &&
        (!('color' in args) || typeof (args as { color: string }).color === 'string')
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new initiative' implies a write/mutation operation, but the description doesn't disclose any behavioral traits like required permissions, whether this is idempotent, what happens on failure, rate limits, or what the response contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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 extremely concise with just three words: 'Create a new initiative'. It's front-loaded with the core action and resource. There's zero wasted language or redundancy. This is appropriately sized for what it communicates.

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?

Given this is a mutation tool (create operation) with 8 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what an 'initiative' is in this context, what happens after creation, error conditions, or return values. The agent would need to guess about the behavioral aspects and output format.

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%, meaning all 8 parameters are documented in the input schema with descriptions. The tool description adds no parameter information beyond what the schema provides. According to the rules, when schema coverage is high (>80%), the baseline score is 3 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 'Create a new initiative' clearly states the action (create) and resource (initiative), which is better than a tautology. However, it doesn't distinguish this tool from sibling tools like linear_createProject or linear_createIssue, which also create different resource types in the same system. The purpose is clear but lacks sibling differentiation.

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 are multiple sibling tools for creating different resources (e.g., linear_createProject, linear_createIssue, linear_createComment), but the description doesn't help an agent choose between them. No context about prerequisites, timing, or exclusions 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