fix(linear): align tool outputs, queries, and pagination with API

[waleedlatif1]

Summary

• Added cursor-based pagination (first/after + pageInfo) to all list tools missing it
• Aligned all GraphQL queries with SDK entity types (added missing fields like updatedAt, createdAt, slugId, revenue, etc.)
• Added shared output property constants to create/update tools that were missing them
• Fixed type interfaces (CustomerStatus, ProjectStatus, Attachment) to match SDK
• Re-added displayName as input-only param for customer status create/update
• Updated block config to pass new params

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 6, 2026 2:33am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR systematically aligns all Linear tool implementations with the Linear GraphQL API and SDK entity types.

Key changes:

• Added cursor-based pagination (first/after + pageInfo) to 13 list operations that were missing it
• Expanded GraphQL queries to include missing SDK fields (updatedAt, createdAt, slugId, revenue, size, progress, sortOrder, status, etc.)
• Introduced shared output property constants in types.ts for consistent tool responses
• Fixed type interfaces: removed displayName from CustomerStatus output (not returned by API), re-added it as input-only parameter for create/update operations
• Updated block config to properly pass pagination parameters to all list tools
• Improved response transformations with proper field mapping (e.g., projectId extraction in milestones)

The changes ensure tools accurately reflect what the Linear API returns and accept, improving data completeness and enabling proper pagination across all list endpoints.

Confidence Score: 5/5

• This PR is safe to merge with no identified issues
• The changes are systematic, well-structured, and focused on aligning with the Linear API. All modifications follow consistent patterns, add missing fields to match SDK types, and properly implement pagination. The code maintains backward compatibility while improving data completeness.
• No files require special attention

Important Files Changed

Filename	Overview
apps/sim/tools/linear/types.ts	Comprehensive type definitions and shared output properties added for better consistency across Linear tools
apps/sim/tools/linear/list_customer_statuses.ts	Added cursor-based pagination and aligned query fields with SDK (removed displayName, added type and updatedAt)
apps/sim/tools/linear/list_project_milestones.ts	Added pagination and expanded query fields (progress, sortOrder, status) with proper projectId mapping
apps/sim/tools/linear/create_customer_status.ts	Added displayName as input-only parameter and expanded output fields (type, updatedAt)
apps/sim/tools/linear/update_project_milestone.ts	Added missing fields, proper projectId mapping, and improved error handling
apps/sim/blocks/blocks/linear.ts	Expanded pagination params to all list operations and properly coerced first param to number

Sequence Diagram

sequenceDiagram
    participant User
    participant Block as Linear Block
    participant Tool as Linear Tool
    participant API as Linear GraphQL API

    Note over User,API: Example: List Customer Statuses with Pagination

    User->>Block: Request list_customer_statuses
    Block->>Block: Coerce first param to Number
    Block->>Tool: Pass params (first, after, accessToken)
    Tool->>Tool: Build GraphQL query with pagination
    Tool->>API: POST /graphql (first: 50, after: cursor)
    API-->>Tool: Return nodes + pageInfo (hasNextPage, endCursor)
    Tool->>Tool: Transform response with pageInfo
    Tool-->>Block: Return {customerStatuses, pageInfo}
    Block-->>User: Output results + pagination info

    Note over User,API: Enhanced with SDK-aligned fields

    User->>Block: Request create_customer_status
    Block->>Tool: Pass params (name, color, displayName)
    Note over Tool: displayName is input-only
    Tool->>API: POST /graphql (create mutation)
    API-->>Tool: Return status (without displayName)
    Note over Tool: Output includes type, updatedAt
    Tool-->>Block: Return SDK-aligned customerStatus
    Block-->>User: Output complete entity

Loading

[greptile-apps]

_{6 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

apps/sim/blocks/blocks/linear.ts
Pagination inputs typed as string

first/after block params are defined as type: 'short-input', which typically yields string values, but many Linear tools declare first as a number param and pass it straight into GraphQL (e.g. variables.first: params.first || 50). If first comes through as a non-empty string (e.g. '10'), params.first || 50 will remain a string and GraphQL will reject it (Int expected). Consider switching first to a numeric input type (if available) or consistently coercing with Number(params.first) in every tool that uses first/after.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/sim/blocks/blocks/linear.ts
Line: 807:810

Comment:
**Pagination inputs typed as string**

`first`/`after` block params are defined as `type: 'short-input'`, which typically yields string values, but many Linear tools declare `first` as a `number` param and pass it straight into GraphQL (e.g. `variables.first: params.first || 50`). If `first` comes through as a non-empty string (e.g. `'10'`), `params.first || 50` will remain a string and GraphQL will reject it (`Int` expected). Consider switching `first` to a numeric input type (if available) or consistently coercing with `Number(params.first)` in every tool that uses `first`/`after`.


How can I resolve this? If you propose a fix, please make it concise.

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[greptile-apps]

_{6 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR