Skip to main content
Glama

Search your library

search
Read-onlyIdempotent

Search the USER'S COLLECTION by title, creator, genre, or theme. Literal keyword match only - the query must actually appear in the item's title/creator/genre/theme text, or it returns nothing. Returns items they own with status, ratings, and for box sets, the list of contained albums. Use this to answer questions about what the user has. For generic, thematic, mood, or conceptual queries (e.g. "something about grief", "a film podcast") where the exact wording may not appear in any field, use search_library instead - it searches by meaning, not keyword.

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": {
      "media_type": "<media_type>",
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (matches title, author/artist/director/creator, genres, or themes)
filterNoFilter by status or rating. Books: all, reading, finished, unread, abandoned, rated, unrated. Movies/shows: all, watching, watched, unwatched, abandoned, rated, unrated. Anime: also plan_to_watch, completed, saved, on_hold, dropped. Albums: all, listening, played, unheard, saved, rated, unrated. Games: all, playing, played, unplayed, saved, on_hold, abandoned, rated, unrated.
media_typeYesType of media to search

Output Schema

NameRequiredDescriptionDefault
itemsYes
queryNo
totalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
    • changedOutput schema / properties / items / items / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
    • changedOutput schema / properties / items / items / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Changed3 schema fields changed
    • changedInput schema / properties / filter / description
      Previous value: -"Filter by status or rating. Books: all, reading, finished, unread, abandoned, rated, unrated. Movies/shows/anime: all, watching, watched, unwatched, abandoned, rated, unrated. Albums: all, listening, played, unheard, saved, rated, unrated."New value: +"Filter by status or rating. Books: all, reading, finished, unread, abandoned, rated, unrated. Movies/shows: all, watching, watched, unwatched, abandoned, rated, unrated. Anime: also plan_to_watch, completed, saved, on_hold, dropped. Albums: all, listening, played, unheard, saved, rated, unrated. Games: all, playing, played, unplayed, saved, on_hold, abandoned, rated, unrated."
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Items from the user's own library matching the request.",
      +  "properties": {
      +    "items": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "cover_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "creator": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "genres": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "media_type": {
      +            "enum": [
      +              "book",
      +              "movie",
      +              "album",
      +              "show",
      +              "anime",
      +              "podcast",
      +              "game",
      +              "manga"
      +            ],
      +            "type": "string"
      +          },
      +          "rating": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "status": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "summary": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "themes": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": [
      +              "array",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "year": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "media_type"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "items"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational detail, which it does: matching is literal substring/keyword only and a non-matching query returns nothing. It also notes box sets return their contained album list, a behavioral quirk not visible in annotations. It stops short of saying anything about result ordering, paging, or empty-result shape, keeping it just below a 5.

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?

Front-loads the core action, then the literal-match caveat, then the return contract, then the alternative — a sensible order with no filler. Slight redundancy in restating "title/creator/genre/theme" twice, but the repetition reinforces the critical failure mode.

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 rich annotations, the description needn't explain return values, and it correctly focuses on matching semantics and tool selection. The only small gap is that it doesn't mention `media_type` being required (it drives which filter values are valid), though the schema enumerates it clearly.

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 description coverage is 100%, so the parameters are already documented; the baseline is therefore 3. The description does add genuine meaning about the `query` parameter — it must literally appear in title/creator/genre/theme text — which is more than the schema says, but the `filter` and `media_type` parameters receive no additional explanation beyond the schema's own enum/status lists.

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?

States a specific verb and resource ("Search the USER'S COLLECTION") plus the searchable fields (title, creator, genre, theme). It explicitly distinguishes itself from the sibling `search_library` by naming that tool and its meaning-based behavior, so an agent can pick the right tool without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("Use this to answer questions about what the user has") and explicit when-NOT-to-use with a concrete condition and examples: thematic/mood queries like "something about grief" should go to `search_library`. The alternative is named along with the reason it differs.

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.

Resources