rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Get Recent Changes

get_recent_changes

Read-onlyIdempotent

Retrieve museum collection records changed within a specified date range. Supports pagination and a lightweight identifiers-only mode for quick change detection, including deleted records.

Instructions

OAI-PMH delta feed of records changed within a date range. Paginated; anchored to a known harvest checkpoint. Use identifiersOnly=true for a lightweight listing (headers only, no full metadata). Full-mode records include an objectNumber for follow-up calls to get_artwork_details or get_artwork_image; identifiersOnly records carry only a LOD URI, so re-run without it to act on a change. Deleted records are flagged with deleted:true (marked [DELETED] in the listing) and carry only a LOD URI + datestamp, no metadata.

Input Schema

TableJSON Schema

Name	Required	Description
`from`	No	Start date in ISO 8601 format (e.g. '2026-02-01T00:00:00Z' or '2026-02-01'). Required for initial request, ignored when resumptionToken is provided.
`until`	No	End date in ISO 8601 format (defaults to now)
`setSpec`	No	Restrict to changes within a specific set
`maxResults`	No	Maximum records to return (1-50, default 10)
`identifiersOnly`	No	If true, returns only record headers (identifier = LOD URI, not objectNumber; datestamp; set memberships) — much faster. Preserved automatically across continuation pages.
`resumptionToken`	No	Pagination token from a previous get_recent_changes result. When provided, all other filters are ignored.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`error`	No
`records`	Yes
`totalChanges`	No
`returnedCount`	Yes
`identifiersOnly`	No
`resumptionToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.90.1Sep 6, 2026

changedInput schema / properties / identifiersOnly / description

Previous value: -"If true, returns only record headers (identifier, datestamp, set memberships) — much faster. Preserved automatically across continuation pages."New value: +"If true, returns only record headers (identifier = LOD URI, not objectNumber; datestamp; set memberships) — much faster. Preserved automatically across continuation pages."

First observedv0.90.0Jul 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behaviors: pagination anchored to a harvest checkpoint, deleted records flagged with deleted:true and [DELETED], identifiersOnly records carrying only a LOD URI, and identifiersOnly being preserved across continuation pages. This materially helps an agent predict results and plan follow-up actions.

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?

The description is dense but front-loaded with the tool's core purpose. Every sentence adds distinct value: delta scope, pagination, identifiersOnly mode, follow-up behavior, and deleted-record handling. No filler or redundancy.

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

Completeness5/5

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

For a six-parameter paginated feed tool, the description covers the critical behavioral context: harvesting workflow, continuation tokens, mode differences, follow-up flow, and deleted-record semantics. An output schema exists, so return-value details do not need to be repeated here.

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 coverage is 100%, so the schema already documents all parameters well. The description adds extra meaning by explaining trade-offs between identifiersOnly and full mode, the follow-up capabilities of objectNumber, and the special shape of deleted records. This goes beyond the parameter descriptions and improves correct parameter choice.

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 clearly identifies the tool as an OAI-PMH delta feed for records changed within a date range, with a specific verb and resource. It also distinguishes its role from sibling tools by framing it around harvest checkpoints and follow-up detail/image calls.

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?

The description gives explicit within-tool guidance: use identifiersOnly=true for lightweight listing, and re-run without it to act on a change. It also explains when full-mode records enable follow-up calls. It does not explicitly state when not to use this tool versus sibling alternatives, but the intended workflow is clear.

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

Deploy Server