Skip to main content
Glama
Sign In
omdb-mcp

omdb-mcp

by Dworf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_by_imdb_id

Look up movie, series, or episode details by IMDb ID. Choose between short or full plot summary.

Instructions

Look up a title by its IMDb ID (e.g. "tt0111161"). OMDb i parameter.

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": {
      "imdb_id": "<imdb_id>"
    },
    "name": "get_by_imdb_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
imdb_idYesIMDb ID, including the "tt" prefix.
plotNo"short" (default) or "full".short

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only says 'look up' without disclosing read-only nature, auth requirements, or API limitations. Minimal behavioral disclosure.

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?

The description is a single concise sentence, front-loaded with the core purpose. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 params, output schema exists), the description is adequate but minimal. It could mention that it returns details for a single title, but the output schema covers that.

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% with descriptions for both parameters. The description adds an example for imdb_id but does not add meaning beyond the schema. 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?

The description clearly states the tool's function: look up a title by IMDb ID, with an example provided. It distinguishes implicitly from siblings which use different identifiers (title, episode, season, search).

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?

The description implies usage when you have an IMDb ID, but does not explicitly state when to use this tool versus alternatives (e.g., get_by_title). No exclusions or prerequisites are mentioned.

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

Deploy Server

Other Tools