Skip to main content
Glama

Itunes Search Search

itunes_search_search
Read-onlyIdempotent

Search the Apple iTunes catalog by keyword across music, movies, podcasts, TV shows, apps, ebooks, and more; filterable by media type, entity, country, and explicit flag; returns up to 200 matching items with metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "Taylor Swift"
    },
    "name": "itunes_search_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen_us | ja_jp (default en_us)
termYesSearch query
limitNo1-200 (default 50)
mediaNomusic | movie | podcast | musicVideo | audiobook | shortFilm | tvShow | software | ebook | all (default all)
entityNoRefines media, e.g. "song", "album", "movieArtist", "tvSeason"
countryNoISO 3166-1 alpha-2 (default us)
explicitNoYes (default) | No, exclude explicit content
attributeNoRestrict matching field, e.g. "artistTerm", "albumTerm", "movieTerm"

Output Schema

NameRequiredDescriptionDefault
resultsYesArray of search result items
resultCountYesNumber of results returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / attribute / description
      Previous value: -"Restrict matching field — e.g. \"artistTerm\", \"albumTerm\", \"movieTerm\""New value: +"Restrict matching field, e.g. \"artistTerm\", \"albumTerm\", \"movieTerm\""
    • changedInput schema / properties / entity / description
      Previous value: -"Refines media — e.g. \"song\", \"album\", \"movieArtist\", \"tvSeason\""New value: +"Refines media, e.g. \"song\", \"album\", \"movieArtist\", \"tvSeason\""
    • changedInput schema / properties / explicit / description
      Previous value: -"Yes (default) | No — exclude explicit content"New value: +"Yes (default) | No, exclude explicit content"
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile needs no restating. The description adds genuine context beyond that: the breadth of the catalog searched and that results are capped at 200 items with metadata, which sets expectations about truncation. It omits any note on rate limits or pagination, so it stops just short of full transparency.

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?

A single front-loaded sentence with the verb and resource first, then filters, then result shape — a sensible information order with no filler. The semicolon-chained clauses are dense but readable, and nothing is redundant with the tool name.

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?

With an output schema present and full parameter documentation, the description only needs to frame scope and result volume, which it does. Its remaining omission — no routing vs. the lookup sibling — is a guidance gap rather than a completeness failure for an eight-parameter 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%, so the schema already documents all eight parameters including enums-like value lists for media, country and explicit. The description only echoes four of them (media, entity, country, explicit) without adding format or interaction details, and says nothing about lang or attribute. Baseline 3 applies when the schema carries the semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the Apple iTunes catalog by keyword') and enumerates the covered media domains, so an agent knows exactly what corpus is queried. It does not name or contrast with the sibling itunes_search_lookup, which is presumably the ID-based counterpart, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

'By keyword' implicitly signals this is the free-text path rather than a lookup, which is a usable usage cue. However, there is no explicit when-to-use/when-not statement, no mention of when to prefer itunes_search_lookup, and no note on prerequisites or expected result volume tradeoffs beyond the 200 cap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.