Skip to main content
Glama

Itunes Search Lookup

itunes_search_lookup
Read-onlyIdempotent

Exact-ID lookup. Provide any one of id / bundle_id / isbn / upc / amg_artist_id / amg_album_id.

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": {
      "id": "909253"
    },
    "name": "itunes_search_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoApple ID(s), comma-separated
upcNoUPC of an album/movie
isbnNoISBN-13 of a book
limitNo
entityNo
countryNo
bundle_idNoiOS / macOS app bundle id
amg_album_idNoAll Music Guide album id
amg_artist_idNoAll Music Guide artist id

Output Schema

NameRequiredDescriptionDefault
resultsYesArray of lookup result items
resultCountYesNumber of results returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
      -  {
      -    "id": "329159963"
      -  },
      -  {
      -    "isbn": "9780316769174"
      -  }
      -]New value: +[
      +  {
      +    "id": "909253"
      +  },
      +  {
      +    "isbn": "9780316769174"
      +  }
      +]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral rule not encoded anywhere in the schema: exactly one ID field should be supplied (schema says required: 0, which would otherwise imply an empty call is valid). It says nothing about what happens if multiple IDs are passed simultaneously or about result cardinality.

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, purpose front-loaded, no filler — the enumeration of ID fields is dense but functional. It could be tightened by stating the one-of rule more compactly, but nothing is genuinely wasted.

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?

For a 9-parameter lookup tool with an output schema, a full annotation set, and no required parameters, the essential missing piece was the one-of identifier rule, and the description supplies it. Remaining gaps (limit/entity/country semantics) are lower-stakes optional filters that an agent can infer from their conventional iTunes Search API meanings.

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 67%, and the description enumerates the same six identifier parameters the schema already describes, so most of it is repetition. Its one real contribution is the one-of constraint across id/bundle_id/isbn/upc/amg_artist_id/amg_album_id, which the schema does not express. The three remaining parameters (limit, entity, country) are undocumented in both schema and description.

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?

"Exact-ID lookup" gives a clear verb (lookup) and qualifier (exact-ID), which implicitly separates it from the fuzzy-search sibling itunes_search_search. It falls short of 5 only because it never names iTunes or the resource being looked up outside the tool name/title.

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?

The phrase "Exact-ID lookup" implies you should come here with a known identifier rather than a query string, which is usable routing guidance. However, no alternative is named explicitly (e.g. "use itunes_search_search for keyword queries") and there is no statement of when this tool would fail or be the wrong choice.

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.