arcade-matter-mcp

Overview Schema Source Related Servers Discussions Admin

ListItems

Matter_ListItems

Read-onlyIdempotent

List items from a Matter library, filtered by status, favorites, tags, content type or update date. Sort by queue, inbox or recent changes and page through results.

Instructions

List items in the user's Matter library, filtered by status, favorites, tags or content type. Use SearchLibrary to find items by words in their text, title, author or site.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (1-100).
`order`	No	Sort order: 'updated' (most recently changed first), 'library_position' (the user's queue order) or 'inbox_position' (newest in the inbox first).
`cursor`	No	Opaque cursor from a previous response's next_cursor, to fetch the next page.
`status`	No	Which part of the library: 'queue' (the reading list), 'inbox' (feeds and newsletters), 'archive' (finished) or 'all'.
`tag_ids`	No	Only return items with any of these tag IDs (e.g. 'tag_k3m9p'). Use ListTags to find them.
`content_types`	No	Only return these content types, e.g. ['article', 'podcast', 'video', 'pdf', 'tweet', 'newsletter'].
`updated_since`	No	Only return items changed after this ISO date or datetime. Highlights and tag changes count as updates.
`favorites_only`	No	Only return favorited items.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the filtering scope, not pagination defaults or truncation behavior; a 3 is appropriate given the annotation coverage.

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, zero waste, with the core capability front-loaded and the alternative routed in the second sentence.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The description is complete enough for correct invocation, though it could note the default order/page size behavior for an 8-parameter list tool.

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 description coverage is 100% and every parameter (limit ranges, enum meanings for order/status, tag_ids usage, cursor paging, updated_since semantics) is already documented in the schema. The description adds no syntax or default-value detail beyond it, so the baseline 3 applies.

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?

States a specific verb (list) and resource (items in the user's Matter library) and enumerates the filter dimensions (status, favorites, tags, content type). It also names the sibling it is not, SearchLibrary, so an agent can distinguish the two without opening either schema.

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?

It gives an explicit routing rule for the alternative (use SearchLibrary for word/title/author/site matches), which is the main disambiguation an agent needs. It does not state prerequisites or explicit exclusions (e.g. that this returns metadata rather than full content), so it stops short of a full 5.

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