Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

linear_getOrganization

Retrieve details about your Linear organization to manage projects and teams effectively through the Linear MCP Server.

Instructions

Get information about the current Linear organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that creates and returns the async executor for the linear_getOrganization tool, delegating to LinearService.getOrganizationInfo()
    export function handleGetOrganization(linearService: LinearService) {
      return async (args: unknown) => {
        try {
          return await linearService.getOrganizationInfo();
        } catch (error) {
          logError("Error getting organization information", error);
          throw error;
        }
      };
    }
  • Tool schema definition for linear_getOrganization, specifying input (empty) and output schema matching organization fields
    export const getOrganizationToolDefinition: MCPToolDefinition = {
      name: "linear_getOrganization",
      description: "Get information about the current Linear organization",
      input_schema: {
        type: "object",
        properties: {},
      },
      output_schema: {
        type: "object",
        properties: {
          id: { type: "string" },
          name: { type: "string" },
          urlKey: { type: "string" },
          logoUrl: { type: "string" }
        }
      }
    };
  • Registration of the linear_getOrganization handler within the registerToolHandlers function that returns the tools map
    linear_getViewer: handleGetViewer(linearService),
    linear_getOrganization: handleGetOrganization(linearService),
    linear_getUsers: handleGetUsers(linearService),
    linear_getLabels: handleGetLabels(linearService),
  • LinearService method that fetches the organization data using LinearClient.organization and returns formatted object with id, name, urlKey, logoUrl, createdAt, and subscription
    async getOrganizationInfo() {
      const organization = await this.client.organization;
      return {
        id: organization.id,
        name: organization.name,
        urlKey: organization.urlKey,
        logoUrl: organization.logoUrl,
        createdAt: organization.createdAt,
        // Include subscription details if available
        subscription: organization.subscription || null,
      };
    }
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. It states it 'Get[s] information' but doesn't disclose behavioral traits such as authentication requirements, rate limits, response format, or whether it's read-only. This is a significant gap for a 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 that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, 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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'information' includes (e.g., organization details, settings, or metadata), leaving gaps in understanding the tool's behavior and output. For a tool with no structured support, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, but that's acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 'Get' and the resource 'information about the current Linear organization', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'linear_getViewer' or 'linear_getTeams', which might also retrieve organizational data, so it misses full sibling distinction.

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 siblings like 'linear_getViewer' (which might return user-specific data) and 'linear_getTeams' (which retrieves team-level info), there's no indication of context or exclusions, leaving usage ambiguous.

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