Skip to main content
Glama

AutoTasker Hub — China Social Data API

itunes_search

iTunes search across music, podcasts, apps, movies: names, artists, artwork, 30s preview URLs. $0.01 USDC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "itunes_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNo
mediaNomusic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful behavioral context — the returned fields (names, artists, artwork, 30s preview URLs) and the per-call cost ("$0.01 USDC") — but says nothing about result limits, defaults, failure modes, or whether the call is read-only.

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 compact sentences with the capability first and the price last; nothing is wasted, though the fragmentary phrasing (bare field lists) is slightly telegraphic rather than fully structured.

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?

For a three-parameter lookup tool with no output schema, the description covers what is searched, what comes back, and what it costs. The remaining gaps are the limit/pagination behavior and the default media filter, which are minor for a tool this simple.

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 0%, so the description must compensate for all three parameters. It partially does by enumerating valid media categories (music, podcasts, apps, movies), which effectively documents the `media` parameter, but says nothing about `term` syntax or the `limit` default (5) and maximum (25).

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 ("iTunes search") plus the covered media types ("music, podcasts, apps, movies"), which lets an agent distinguish it from the arxiv/npm/pubmed-style search siblings at a glance. It stops short of explicitly naming or contrasting any sibling, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no routing advice relative to the other *_search tools. The only implied usage is 'find iTunes content,' which an agent must infer from the media listing alone.

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.