rijksmuseum-mcp+

Overview Schema Source Related Servers Discussions Admin

Find Artworks Citing a Publication

find_artworks_citing_publication

Read-onlyIdempotent

Find artworks that cite a given publication by entering its URI or ID. Use a publication ID from artwork bibliography to retrieve citing works.

Instructions

Reverse bibliography: artworks citing a given publication URI or id. Use the publicationUri from get_artwork_bibliography (e.g. 'https://id.rijksmuseum.nl/301154354') or the bare id. Local and resolver-free. Not for topic search of the library catalogue.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`full`	No	If true, return ALL citing artworks. Default: first 20 + total count.
`publication`	Yes	Publication URI (https://id.rijksmuseum.nl/301…) or the bare publication id.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`total`	Yes
`artworks`	Yes	Artworks whose bibliography cites this publication. Empty when none (or bibliography not harvested).
`warnings`	No
`publicationId`	Yes
`publicationUri`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.90.1Sep 6, 2026
- removedOutput schema / properties / artworks / items / properties / creator / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / artworks / items / properties / creator / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedv0.90.0Jul 4, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructiveness, so the description does not need to repeat those. It adds useful behavioral context beyond the annotations: 'Local and resolver-free' clarifies that no external resolver is needed, and the reverse-bibliography framing explains what kind of lookup this performs.

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?

Three short sentences carry all essential information: purpose, input provenance with example, and an exclusion. It is front-loaded with the core meaning and contains no filler.

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 annotations, schema descriptions, output schema, and the two-parameter simplicity, the description covers everything an agent needs to invoke the tool correctly. It explains the input source, the intended usage, and what the tool is not for, making it complete for this context.

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 baseline is 3. The description adds value by providing a concrete example URI and explicitly tying the publication parameter to the output of get_artwork_bibliography, which helps the agent construct a valid input even beyond the schema's description.

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 a specific verb and resource: finding artworks that cite a given publication URI or id. The phrase 'Reverse bibliography' immediately distinguishes it from related tools, and the explicit 'Not for topic search of the library catalogue' prevents confusion with search_artwork.

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

Usage Guidelines5/5

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

The description gives concrete guidance on what input to use and where to obtain it: 'Use the publicationUri from get_artwork_bibliography'. It also states an explicit when-not condition, 'Not for topic search of the library catalogue,' which helps an agent choose between this and sibling tools.

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

Deploy Server