Skip to main content
Glama

linear_updateSavedView

Modify a saved view in Linear by providing the view ID and updating fields like name, filters, or sharing settings.

Instructions

Update a Linear saved view (API: updateCustomView). Provide id plus at least one other field to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the saved view to update
nameNoUpdated saved view name
descriptionNoUpdated saved view description. Pass null to clear it.
sharedNoWhether the saved view is shared across the organization
iconNoUpdated icon for the saved view. Pass null to clear it.
colorNoUpdated icon color for the saved view. Pass null to clear it.
teamIdNoUpdated team associated with the saved view. Pass null to clear it.
projectIdNoUpdated project associated with the saved view. Pass null to clear it.
ownerIdNoUpdated owner for the saved view. Pass null to clear it.
filtersNoUpdated raw filters object to store on the saved view. Pass null to clear it.
filterDataNoUpdated issue filter data for the saved view. Pass null to clear it.
projectFilterDataNoUpdated project filter data for the saved view. Pass null to clear it.
Behavior3/5

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

No annotations so description carries full burden. States update action and required parameter combination but lacks details on auth, idempotency, or side effects.

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?

Two sentences, no waste, front-loaded purpose and usage instruction.

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?

No output schema, no return value description; complex parameter set (null semantics, many optional fields) needs more behavioral context.

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?

Schema covers all 12 parameters; description adds cross-parameter constraint (id plus one other field), improving semantics beyond individual schema descriptions.

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 'Update' and specific resource 'Linear saved view' plus API endpoint reference distinguishes from create and delete siblings.

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

Usage Guidelines4/5

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

Explicit instruction to provide id and at least one other field gives clear usage context, though alternatives are not directly mentioned.

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