omdb_by_id
Retrieve movie or show details from the OMDB database using an IMDb ID.
Instructions
Get an OMDB movie/show by IMDb ID.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| i | Yes | IMDb ID | |
| api_key | No |
Retrieve movie or show details from the OMDB database using an IMDb ID.
Get an OMDB movie/show by IMDb ID.
| Name | Required | Description | Default |
|---|---|---|---|
| i | Yes | IMDb ID | |
| api_key | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only states it is a GET operation; no disclosure of rate limits, authentication needs, error handling, or other behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, concise sentence that is front-loaded and contains no unnecessary words. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple lookup tool, but lacks output description, error handling, and guidance on the 'api_key' parameter. With no output schema, the description should do more.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 50% (only 'i' has a description). The tool description adds no parameter information, leaving 'api_key' undocumented and failing to compensate for the gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the verb 'Get', the resource 'OMDB movie/show', and the method 'by IMDb ID'. It differentiates from sibling tools omdb_by_title and omdb_search by specifying the ID lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage: use when you have an IMDb ID. However, no explicit guidance on when not to use or alternatives like omdb_by_title or omdb_search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'
If you have feedback or need assistance with the MCP directory API, please join our Discord server