Skip to main content
Glama

VHS Label Maker — texs.org

Search movies, shows, games and albums

search_content
Read-only

Look up a movie, TV show, video game or music album by title and return candidate matches with years. Use when the user's title is ambiguous and you want to confirm which one they mean before composing.

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": {
      "type": "<type>",
      "query": "<query>"
    },
    "name": "search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesmovie, tv, game (video games, IGDB) or album
queryYesTitle to search for, e.g. "Predator 1987" or "Michael Jackson Thriller"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"movie, tv, or album"New value: +"movie, tv, game (video games, IGDB) or album"
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "movie",
      -  "tv",
      -  "album"
      -]New value: +[
      +  "movie",
      +  "tv",
      +  "game",
      +  "album"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety and open-world behavior are covered. The description adds that results are candidate matches with years rather than a single resolved record — useful since there is no output schema — but says nothing about match count, no-match behavior, or what identifiers come back.

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

Conciseness5/5

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

Two sentences with zero filler: the first defines what the tool returns, the second defines when to reach for it. Purpose is front-loaded ahead of usage guidance, which is the right ordering.

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?

This is a low-complexity, two-parameter read tool with full annotation coverage and a complete schema, so the bar is modest. The description covers purpose, trigger and result shape; only the follow-up routing (which tool to call once the title is confirmed) and no-match behavior are left implicit.

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%, with the type enum and the query parameter both documented in the schema, including title examples. The description only restates that search is by title, adding no format or parsing guidance beyond what the schema already provides, so the baseline 3 applies.

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 ("Look up a movie, TV show, video game or music album by title") and names the return shape ("candidate matches with years"), which clearly separates it from an exact-fetch tool like get_content. It stops short of naming the sibling to use after disambiguation, so it is clear but not fully differentiated.

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?

Gives an explicit trigger: "Use when the user's title is ambiguous and you want to confirm which one they mean before composing." That covers the primary when-to-use case, but there is no when-not guidance (e.g., don't call when the title is already unambiguous and an exact lookup would do).

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