Skip to main content
Glama

linear_addProjectToInitiative

Link a project to an initiative in Linear to organize related work under strategic goals. Specify the initiative and project IDs to establish the connection.

Instructions

Add a project to an initiative

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
initiativeIdYesThe ID of the initiative
projectIdYesThe ID of the project to add

Implementation Reference

  • The core handler function for the linear_addProjectToInitiative tool. Validates input using type guard and delegates to LinearService.addProjectToInitiative.
    export function addProjectToInitiativeHandler(linearService: LinearService) {
      return async (args: unknown) => {
        if (!isAddProjectToInitiativeInput(args)) {
          throw new Error('Invalid input for addProjectToInitiative');
        }
    
        console.log(
          `[addProjectToInitiative] Adding project ${args.projectId} to initiative ${args.initiativeId}`,
        );
        const result = await linearService.addProjectToInitiative(args.initiativeId, args.projectId);
        console.log(`[addProjectToInitiative] Project added successfully`);
        return result;
      };
    }
  • MCP tool definition including input and output schemas for linear_addProjectToInitiative.
      name: 'linear_addProjectToInitiative',
      description: 'Add a project to an initiative',
      input_schema: {
        type: 'object',
        properties: {
          initiativeId: {
            type: 'string',
            description: 'The ID of the initiative',
          },
          projectId: {
            type: 'string',
            description: 'The ID of the project to add',
          },
        },
        required: ['initiativeId', 'projectId'],
      },
      output_schema: {
        type: 'object',
        properties: {
          success: { type: 'boolean' },
          project: {
            type: 'object',
            properties: {
              id: { type: 'string' },
              name: { type: 'string' },
              initiative: {
                type: 'object',
                properties: {
                  id: { type: 'string' },
                  name: { type: 'string' },
                },
              },
            },
          },
        },
      },
    },
  • Registration of the tool handler in the main tool handlers map.
    linear_addProjectToInitiative: addProjectToInitiativeHandler(linearService),
  • Type guard function used in the handler to validate input arguments for linear_addProjectToInitiative.
    export function isAddProjectToInitiativeInput(args: unknown): args is {
      initiativeId: string;
      projectId: string;
    } {
      return (
        typeof args === 'object' &&
        args !== null &&
        'initiativeId' in args &&
        typeof (args as { initiativeId: string }).initiativeId === 'string' &&
        'projectId' in args &&
        typeof (args as { projectId: string }).projectId === 'string'
      );
    }
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 but offers minimal information. It implies a write operation ('Add') but doesn't specify permissions required, side effects (e.g., if this affects project visibility or triggers notifications), error conditions, or response format. This is inadequate for a mutation tool without annotation support.

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, direct sentence with zero wasted words, making it easy to parse and front-loaded with the core action. Every word earns its place by conveying the essential purpose without redundancy or fluff.

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 the complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as behavioral traits (e.g., idempotency, error handling), return values, or usage constraints, leaving significant gaps for an AI agent to operate safely and 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 both parameters clearly documented in the schema itself. The description adds no additional meaning beyond what the schema provides (e.g., format of IDs, validation rules, or relationship implications), so it meets the baseline for high schema coverage without compensating 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 ('Add') and the target resource ('a project to an initiative'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'linear_addIssueToProject' or 'linear_removeProjectFromInitiative' beyond the basic verb-noun combination, which prevents a perfect score.

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 (e.g., existing initiative and project), exclusions, or relationships with sibling tools like 'linear_removeProjectFromInitiative' or 'linear_getInitiativeProjects', leaving the agent to infer context from tool names alone.

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