Boxlist

Search Boxlist titles

search_titles

Read-onlyIdempotent

Find films, TV series, books and video games in the Boxlist catalogue by name (books also by author). Returns each title's boxlist.com page and a ref to pass to the other Boxlist tools. Use it to pin down the right title (e.g. which "Dune") before asking for a taste profile or similar titles.

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

Input Schema

Name	Required	Description
`limit`	No	How many results (1-5, default 5).
`media`	No	Restrict to these media: "film", "tv", "book", "game". Omit for all four.
`query`	Yes	Title or part of it, optionally with a year ("Dune 2021"). Books also match by author.

Output Schema

Name	Required	Description
`note`	Yes
`query`	Yes
`results`	Yes
`nextStep`	Yes
`attribution`	Yes	Required credit: show "Data from Boxlist" with the link wherever these results are used.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: results carry a boxlist.com page and a `ref` that chains into the other Boxlist tools, which is the key data-flow fact for an agent. It does not mention ranking or match quality, which is a modest gap.

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?

Three sentences, front-loaded with what is searched and what comes back, then closing with the routing advice. Tight overall, though the return-value sentence partially duplicates what the output schema already conveys.

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 simple three-parameter lookup tool with full schema coverage, an output schema, and complete annotations, this description covers purpose, result payload, and downstream chaining. Nothing an agent needs in order to call it correctly is missing.

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%, and the schema already documents query format, the year suffix, the media enum, and the 1-5 limit. The description's 'books also by author' and the 'Dune 2021' example restate schema content rather than extending it, so the baseline of 3 is appropriate.

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 ('Find films, TV series, books and video games in the Boxlist catalogue by name'), plus a notable qualifier that books also match by author. This makes the tool immediately distinguishable from the sibling tools, which operate on a `ref` rather than a name query.

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 clear sequencing guidance: use it to 'pin down the right title (e.g. which "Dune") before asking for a taste profile or similar titles', which implicitly routes to get_title_taste_profile and find_similar_in_feel. It stops short of stating any explicit when-not-to-use case or ambiguity handling (e.g. no match found).

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

All Boxlist tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?