Remove a saved Linear view using its ID to declutter your workspace and keep only relevant views.
Delete a Linear saved view (API: deleteCustomView)
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the saved view to delete |
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| success | No |
Changes observed during successful MCP inspections.
v1.4.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true, indicating the mutation behavior. The description adds the API name but does not elaborate on side effects, reversibility, or error conditions. It provides minimal additional context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that conveys the essential information without any unnecessary words or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation with one parameter and an output schema, the description is mostly complete. The only gap is the lack of context about prerequisites or consequences, but given the tool's simplicity, this is acceptable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage, describing the 'id' parameter as 'ID of the saved view to delete'. The description adds no further semantics or format details, so it meets the baseline but does not exceed it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Delete' and the resource 'saved view', and also references the underlying API method 'deleteCustomView'. This distinguishes it from sibling tools like create and update, which have different verbs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide any guidance on when to use this tool versus alternatives, such as when to delete a saved view as opposed to archiving or updating it. No prerequisites or exclusions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.