Skip to main content
Glama

Search Met Museum Artworks

met.art.search
Read-onlyIdempotent

Search The Metropolitan Museum of Art's 470,000+ artworks by keyword, artist, medium, department, date range, or geography. Returns object IDs for full metadata and images.

Instructions

Search 470,000+ artworks at The Metropolitan Museum of Art by keyword, artist, medium, department, date range, or geography. Returns object IDs — use met.details for full metadata and images. CC0 public domain (Met Museum)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch keyword — artist, title, medium, or subject (e.g. "monet", "sunflowers", "greek vase", "armor")
department_idNoDepartment filter: 1=American Decorative Arts, 3=Ancient Near Eastern Art, 6=Asian Art, 9=Drawings and Prints, 11=European Paintings, 13=Greek and Roman Art, 17=Medieval Art, 21=Modern Art
mediumNoMedium filter (e.g. "Paintings", "Sculpture", "Photographs", "Ceramics")
has_imagesNoOnly return artworks with images (default: true)
geo_locationNoGeographic location filter (e.g. "France", "Japan", "Egypt")
date_beginNoStart year for date range filter (e.g. 1800). Use with date_end.
date_endNoEnd year for date range filter (e.g. 1900). Use with date_begin.

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 declare readOnlyHint, destructiveHint, and idempotentHint. Description adds that artworks are CC0 public domain, which is useful context for usage rights. No contradiction with annotations.

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 concise sentences: first states purpose and scope, second clarifies output and chaining, third notes public domain. Efficiently front-loaded with no redundant information.

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?

Covers key aspects: scope, search dimensions, output type, chaining, and licensing. Does not address pagination or sorting, but given the output schema likely provides structure, this is acceptable for a search 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 coverage is 100% with well-described parameters. The description enumerates search dimensions (keyword, artist, medium, etc.) but does not add meaning beyond the schema. Baseline score of 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?

Clearly states it searches 470,000+ artworks at the Met Museum by various criteria and returns object IDs. Distinguishes from sibling met.art.details by explicitly directing to that tool for full metadata and images.

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?

Provides clear guidance to use met.art.details for full metadata and images after obtaining object IDs. Does not explicitly mention when not to use, but the complementary nature is well communicated.

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