Skip to main content
Glama

Omdb

by io.github.pipeworx-io

Search Titles

search_titles
Read-onlyIdempotent

Keyword search across OMDb movies, series, and episodes. Returns up to 10 results per page with title, year, IMDB ID, type (movie/series/episode), and poster URL. Filter by release year or type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-100 (default 1)
typeNomovie | series | episode
yearNoRestrict to a release year
queryYesTitle keyword

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query keyword
totalYesTotal number of results available
resultsYesArray of search results (up to 10 per page)
returnedYesNumber of results returned in this response

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Inception"
+  },
+  {
+    "page": 1,
+    "query": "Breaking Bad",
+    "type": "series",
+    "year": 2008
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "The search query keyword",
+      "type": "string"
+    },
+    "results": {
+      "description": "Array of search results (up to 10 per page)",
+      "items": {
+        "properties": {
+          "imdb_id": {
+            "description": "IMDB ID (tt-prefixed)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "poster": {
+            "description": "Poster image URL or null if unavailable",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Movie/series/episode title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "description": "Type: movie, series, or episode",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "year": {
+            "description": "Release year",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results returned in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of results available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "query",
+    "total",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds useful behavioral details such as 'Returns up to 10 results per page' and mentions filtering by year/type. Annotations already provide readOnlyHint, idempotentHint, etc., so description complements them well.

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, front-loaded with key action, no wasted words. Efficiently covers purpose and key constraints.

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?

Given output schema exists, description sufficiently covers purpose, parameters, behavior (pagination, filtering), and return fields. Complete for moderate complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 4 parameters. Description adds context about keyword search and filtering capabilities, plus mentions return fields beyond schema.

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?

Clearly states 'Keyword search across OMDb movies, series, and episodes' and specifies return fields. Distinguishes from sibling tools like get_by_title and get_by_imdb_id which are exact match lookups.

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

Usage Guidelines3/5

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

Implies use for broad keyword search, but does not explicitly state when to use this vs alternatives like get_by_title or when not to use. No exclusion guidance provided.

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

All Omdb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_grounded, and deep_research all answering questions, and bet_research overlapping with polymarket_edges/arbitrage. The diverse tool set lacks clear boundaries.

Naming Consistency3/5

All names use snake_case, but verb patterns are inconsistent: some start with verbs (ask_pipeworx, remember) while others start with nouns (polymarket_arbitrage, entity_profile). Names vary widely in length and descriptiveness.

Tool Count2/5

33 tools is excessive for a server named 'Omdb', which implies a movie database. Most tools are unrelated to movies, indicating poor scoping for the server's purpose.

Completeness2/5

For the OMDb domain, only search and retrieval tools exist, with no create/update/delete operations. Overall, the tool set feels like a random collection with significant gaps relative to any coherent domain.

Resources