Skip to main content
Glama

linear_updateInitiative

Modify an existing initiative's details such as name, description, status, target date, owner, or visual attributes in Linear project management.

Instructions

Update an existing initiative

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initiativeIdYesThe ID of the initiative to update
nameNoUpdated name of the initiative
descriptionNoUpdated description of the initiative
contentNoUpdated content in markdown format
ownerIdNoUpdated owner ID
targetDateNoUpdated target completion date (ISO 8601 format)
statusNoUpdated status of the initiative
iconNoUpdated icon emoji
colorNoUpdated color in hex format

Implementation Reference

  • The main handler function for the linear_updateInitiative tool. It validates the input using a type guard, extracts initiativeId and updateData, calls the LinearService to update the initiative, and returns the result.
    export function updateInitiativeHandler(linearService: LinearService) {
      return async (args: unknown) => {
        if (!isUpdateInitiativeInput(args)) {
          throw new Error('Invalid input for updateInitiative');
        }
    
        const { initiativeId, ...updateData } = args;
        console.log(`[updateInitiative] Updating initiative: ${initiativeId}`);
        const result = await linearService.updateInitiative(initiativeId, updateData);
        console.log(`[updateInitiative] Initiative updated successfully`);
        return result;
      };
    }
  • The tool definition including input and output schemas for linear_updateInitiative.
    {
      name: 'linear_updateInitiative',
      description: 'Update an existing initiative',
      input_schema: {
        type: 'object',
        properties: {
          initiativeId: {
            type: 'string',
            description: 'The ID of the initiative to update',
          },
          name: {
            type: 'string',
            description: 'Updated name of the initiative',
          },
          description: {
            type: 'string',
            description: 'Updated description of the initiative',
          },
          content: {
            type: 'string',
            description: 'Updated content in markdown format',
          },
          ownerId: {
            type: 'string',
            description: 'Updated owner ID',
          },
          targetDate: {
            type: 'string',
            description: 'Updated target completion date (ISO 8601 format)',
          },
          status: {
            type: 'string',
            description: 'Updated status of the initiative',
            enum: ['notStarted', 'inProgress', 'completed', 'paused'],
          },
          icon: {
            type: 'string',
            description: 'Updated icon emoji',
          },
          color: {
            type: 'string',
            description: 'Updated color in hex format',
          },
        },
        required: ['initiativeId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          id: { type: 'string' },
          name: { type: 'string' },
          description: { type: 'string' },
          status: { type: 'string' },
          url: { type: 'string' },
        },
      },
    },
  • Registration of the linear_updateInitiative tool handler in the registerToolHandlers function.
    linear_updateInitiative: updateInitiativeHandler(linearService),
  • Type guard function used in the handler to validate input arguments for linear_updateInitiative.
     * Type guard for linear_updateInitiative tool arguments
     */
    export function isUpdateInitiativeInput(args: unknown): args is {
      initiativeId: string;
      name?: string;
      description?: string;
      content?: string;
      ownerId?: string;
      targetDate?: string;
      status?: string;
      icon?: string;
      color?: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'initiativeId' in args &&
        typeof (args as { initiativeId: string }).initiativeId === 'string' &&
        (!('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 full burden for behavioral disclosure. 'Update an existing initiative' implies a mutation operation but reveals nothing about permissions needed, whether changes are reversible, rate limits, error conditions, or what happens to unspecified fields. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero wasted words. It's appropriately sized and front-loaded with the core action, making it easy to parse quickly.

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 9 parameters, no annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects like side effects, error handling, or response format, leaving significant gaps in understanding how to use this tool effectively.

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%, with all 9 parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline of 3 for high schema coverage without adding 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 ('Update') and resource ('an existing initiative'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling update tools like linear_updateIssue or linear_updateProject, which follow the same pattern.

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. It doesn't mention prerequisites (like needing initiativeId), when not to use it (e.g., for creation vs. update), or how it relates to sibling tools like linear_createInitiative or linear_archiveInitiative.

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