Paperless MCP

Get Saved View

get_saved_view

Read-onlyIdempotent

Retrieve a saved view by ID to access its configured filters, ordering, and display options.

Instructions

Fetch a saved view by ID.

Visibility flags are null when payload v10 omits those preferences.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`owner`	No
`page_size`	No
`sort_field`	No
`filter_rules`	No
`sort_reverse`	No
`show_in_sidebar`	No
`show_on_dashboard`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.1.0Sep 21, 2026
- addedOutput schema / properties / show_in_sidebar / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedOutput schema / properties / show_in_sidebar / default
```
Previous value: -falseNew value: +null
```
- removedOutput schema / properties / show_in_sidebar / type
```
Removed value: -"boolean"
```
- addedOutput schema / properties / show_on_dashboard / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedOutput schema / properties / show_on_dashboard / default
```
Previous value: -falseNew value: +null
```
- removedOutput schema / properties / show_on_dashboard / type
```
Removed value: -"boolean"
```
First observedv1.0.1Jul 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds a specific behavioral nuance about visibility flags being null when payload v10 omits those preferences, which is context beyond the annotations. No contradiction detected.

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 with zero waste. The primary purpose is front-loaded, and the second sentence adds a targeted behavioral detail. No unnecessary elaboration.

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?

For a simple get-by-ID tool with an output schema and comprehensive safety annotations, the description covers the key nuance (null visibility flags). No critical missing information; mentioning the sibling list_saved_views would be nice but is not essential for correctness.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only says 'by ID', which does not clarify what a saved view is, any constraints, or the meaning of view_id beyond the schema's integer type. The description adds minimal value to parameter understanding.

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?

The description states a specific verb ('Fetch'), a resource ('saved view'), and identifies the parameter as ID. It clearly distinguishes from sibling list_saved_views by focusing on retrieving a single view by identifier. The purpose is unambiguous.

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

Usage Guidelines3/5

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

The description implies usage when a view_id is available but does not explicitly state when to use this versus alternatives like list_saved_views, nor does it mention exclusions or prerequisites. Guidance is minimal and left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server