Skip to main content
Glama
kintopp

rijksmuseum-mcp+

by kintopp

Get Recent Changes

get_recent_changes
Read-onlyIdempotent

Retrieve records changed within a date range from the Rijksmuseum collection, with pagination and optional lightweight listing of identifiers only.

Instructions

OAI-PMH delta feed — records changed within a date range since a known harvest checkpoint, paginated. Use identifiersOnly=true for a lightweight listing (headers only, no full metadata). Each record includes an objectNumber for follow-up calls to get_artwork_details or get_artwork_image. 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
NameRequiredDescriptionDefault
fromNoStart 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.
untilNoEnd date in ISO 8601 format (defaults to now)
setSpecNoRestrict to changes within a specific set
maxResultsNoMaximum records to return (1-50, default 10)
identifiersOnlyNoIf true, returns only record headers (identifier, datestamp, set memberships) — much faster. Preserved automatically across continuation pages.
resumptionTokenNoPagination token from a previous get_recent_changes result. When provided, all other filters are ignored.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
errorNo
recordsYes
totalChangesNo
returnedCountYes
identifiersOnlyNo
resumptionTokenNo
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds useful context about deleted records being flagged with 'deleted:true' and pagination via resumptionToken, going beyond what annotations provide.

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 concise, front-loaded with the main purpose, and every sentence adds necessary information. No redundant or verbose content.

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?

Given the output schema exists and annotations are present, the description covers purpose, filtering, pagination, deleted records, and follow-up usage. It is complete for the tool's complexity.

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 already covers all 6 parameters with 100% description. The description adds value by explaining the effect of identifiersOnly, the presence of objectNumber for follow-up, and that resumptionToken overrides other filters.

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 states the tool as an 'OAI-PMH delta feed' for records changed within a date range, paginated, with options for identifiers-only and handling of deleted records. It distinguishes from sibling tools like get_artwork_details by mentioning follow-up usage.

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 provides specific guidance on when to use identifiersOnly=true for lightweight listing and mentions follow-up tools. However, it lacks explicit alternatives or when-not-to-use compared to other tools like search_artwork.

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/kintopp/rijksmuseum-mcp-plus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server