Skip to main content
Glama

search_album_cover

Retrieve canonical album cover art from MusicBrainz, iTunes, and Spotify. All results are editorial-licensed and suitable for album identification interfaces.

Instructions

Find canonical album artwork. Uses MusicBrainz Cover Art Archive + iTunes + Spotify. Results are EDITORIAL_LICENSED — safe for album identification UI per platform ToS; always show attribution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artistYes
albumYes
providersNo
safeSearchNo
licensePolicyNo
maxPerProviderNo
minWidthNo
minHeightNo
timeoutMsNo

Implementation Reference

  • Core implementation of searchAlbumCover. Delegates to searchImages with preset providers ['musicbrainz-caa', 'itunes', 'spotify', 'wikimedia'] and maxPerProvider of 5.
    export async function searchAlbumCover(
      artist: string,
      album: string,
      opts: SearchOptions = {},
    ): Promise<SearchResultBundle> {
      return searchImages(`${artist} ${album}`, {
        ...opts,
        providers: opts.providers ?? ["musicbrainz-caa", "itunes", "spotify", "wikimedia"],
        maxPerProvider: opts.maxPerProvider ?? 5,
      });
    }
  • MCP tool registration for 'search_album_cover'. Describes the tool, binds the schema, and calls the core searchAlbumCover function, rendering results via renderSearch.
    {
      name: "search_album_cover",
      description:
        "Find canonical album artwork. Uses MusicBrainz Cover Art Archive + iTunes + Spotify. Results are EDITORIAL_LICENSED — safe for album identification UI per platform ToS; always show attribution.",
      inputSchema: searchAlbumCoverSchema,
      async handler(args) {
        const out = await searchAlbumCover(args.artist, args.album, args);
        return renderSearch(out.candidates, out.providerReports, out.warnings);
      },
    },
  • Zod input schema for search_album_cover tool. Validates artist (string), album (string), plus common search options.
    export const searchAlbumCoverSchema = z.object({
      artist: z.string().min(1),
      album: z.string().min(1),
      ...commonSearchOpts,
    });
  • Tool registration: name 'search_album_cover' with inputSchema: searchAlbumCoverSchema in the TOOLS array.
    name: "search_album_cover",
    description:
      "Find canonical album artwork. Uses MusicBrainz Cover Art Archive + iTunes + Spotify. Results are EDITORIAL_LICENSED — safe for album identification UI per platform ToS; always show attribution.",
    inputSchema: searchAlbumCoverSchema,
  • Import of searchAlbumCover from 'webfetch-core' (packages/core/src/hints/album-covers.ts).
    searchAlbumCover,
Behavior4/5

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

Discloses that results are editorial-licensed and safe per ToS, which is key behavioral info. No annotations provided, so description covers safety. Could add more on failure modes or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, efficient and front-loaded. However, lacks structure or parameter hints. No wasted words, but could be slightly more informative.

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

Completeness3/5

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

With 9 parameters and no output schema, description is incomplete. It doesn't explain return format or behavior for missing results. Adequate for a simple search but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; description does not mention any parameters despite there being 9, including required ones. Schema is detailed, but description fails to add meaning beyond it.

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?

Description uses specific verb 'Find' and resource 'canonical album artwork', clearly distinguishing from sibling tools like search_images and search_artist_images. Mentions specific data sources (MusicBrainz, iTunes, Spotify) and licensing.

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?

States use case 'album identification UI' and attribution requirement. Implicitly differentiates from siblings but lacks explicit when-to-use vs alternatives. Clear context provided.

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/ashlrai/webfetch'

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