Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tmdb_search

Read-only

Searches TMDB movies, TV shows, people, and collections. An unscoped query interleaves results across all four types rather than returning whichever type happens to rank first upstream. Credential-free public TMDB data. limit: Max results, default 10, max 20. page: 1-based results page, default 1. Use tmdb_movie_list to get a TMDB movie chart.

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": "tmdb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based results page, default 1.
typeNoOptional result type filter: movie, tv, person, or collection. Omit for mixed results.
limitNoMax results, default 10, max 20.
queryYesSearch query.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: interleaved result behavior for unscoped queries and credential-free public data access. It does not describe pagination edge cases or result ordering beyond the interleave note.

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 purpose and the distinctive interleave behavior, then packs params and the sibling pointer into a compact block. Slightly dry but no wasted sentences; the param restatements are the only marginal content.

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, the description needn't explain return values, and it correctly avoids that. It covers purpose, the type-filter behavior, credential-free access, and one sibling alternative, leaving only edge-case pagination details unaddressed.

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 100%, so the schema already documents query, type, limit, and page with defaults and max values. The description only restates the limit and page defaults rather than adding format or syntax guidance, which is the correct baseline when the schema does the heavy lifting.

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 (Searches) and multi-type resource (TMDB movies, TV shows, people, collections). The note that an unscoped query 'interleaves results across all four types' distinguishes its behavior from a single-type search, and it explicitly names the sibling tmdb_movie_list for chart-style lookups.

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?

Names the alternative tmdb_movie_list and when to use it ('to get a TMDB movie chart'), which is a concrete routing rule. It also implies when to omit the type filter for mixed results, though it stops short of full when/when-not coverage across the other three TMDB search siblings.

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

All Crawlora MCP toolsInspect
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