Skip to main content
Glama

Search Cleveland Museum Collection

cma.art.search
Read-onlyIdempotent

Search the Cleveland Museum of Art's collection of 64,000+ artworks by keyword, artist, type, or department. Filter results to show only CC0-licensed images for commercial use. Retrieve artwork IDs, titles, artists, dates, and image URLs.

Instructions

Search 64,000+ artworks at the Cleveland Museum of Art by keyword, artist, type, or department. Filter for CC0-only (commercial-free) images. Returns artwork IDs, title, artist, date, license status, image URLs. Use cma.artwork for full details (CMA, CC0)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch keyword — artist, title, subject (e.g. "monet", "armor", "japanese")
typeNoArtwork type filter (e.g. "Painting", "Sculpture", "Print", "Photograph")
departmentNoDepartment filter (e.g. "European Painting and Sculpture", "Asian Art", "Prints")
artistNoArtist name filter (e.g. "Claude Monet", "Pablo Picasso")
cc0_onlyNoOnly return CC0-licensed artworks (free for commercial use). Default: false.
has_imageNoOnly return artworks with images (default: true)
limitNoNumber of results (1-50, default 20)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds value by listing the specific fields returned (IDs, title, artist, date, license status, image URLs), which is not fully captured in the input schema.

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 two short sentences with no extraneous information. It is front-loaded with the core function and includes a usage hint, making it very efficient.

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?

Given the 7 optional parameters and output schema existence, the description adequately covers the tool's capabilities. It could mention pagination or result format, but the returned fields are listed, making it fairly complete.

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?

The input schema already covers all 7 parameters with descriptions. The description mentions query and cc0_only but does not add significant new meaning beyond the schema. Baseline score of 3 due to high schema coverage.

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 searches artworks at the Cleveland Museum of Art, listing specific filter dimensions (keyword, artist, type, department) and return fields. It distinguishes from the sibling tool cma.art.details for full details.

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 advises using cma.artwork (likely cma.art.details) for full details after search, providing a clear workflow. However, it does not explicitly mention when not to use this tool or alternatives like other museum search tools on the same server.

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/whiteknightonhorse/APIbase'

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