Skip to main content
Glama

bulk_save_issues

Batch update multiple Linear issues with common fields in one round-trip, using a required confirmation phrase to prevent unintended mass changes.

Instructions

Apply the same update to multiple issues in one round-trip.

ids is a list of issue UUIDs. Every other arg is an optional field to set on all of them (skip args you don't want to change). Linear's issueBatchUpdate mutation does the work server-side — way faster than N separate save_issue calls for bulk ops like "mark these 50 as Done" or "reassign these to me."

auth_phrase (REQUIRED, v0.3) must be one of: "go", "yes do it", "confirmed", "execute", "go cancel", "go update". Without this explicit confirmation a single hallucinated arg could mass-modify pre-existing shared workspace data — surface the requirement to the operator and capture their explicit phrase before calling this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
cycle_idNo
due_dateNo
estimateNo
priorityNo
state_idNo
label_idsNo
workspaceNo
project_idNo
assignee_idNo
auth_phraseYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses server-side mutation, destructive potential, and the auth safety mechanism. Lacks details on return value or concurrency, but output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three clear paragraphs with code formatting for params. Efficient but includes some redundancy (auth_phrase explanation repeated in schema). Front-loaded with core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core functionality and critical safety. Does not explain return values or errors, but output schema exists. For the complexity of 11 params and no annotations, it is nearly complete.

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 coverage is 0%, so description should compensate. It explains ids and auth_phrase well but only mentions other params are optional without describing their meaning. Parameter names are self-explanatory, but description adds minimal value beyond naming.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb 'apply the same update to multiple issues' with specific resource 'issues' and explicit efficiency advantage over save_issue. Distinguishes from sibling save_issue by highlighting batch update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: for bulk operations like 'mark these 50 as Done' and compares to save_issue. Also specifies the required auth_phrase and the need to omit unchanged fields.

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/adelaidasofia/linear-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server