GuideDoc Documentary Database

Read full public documentary details

get_documentary

Read-only

Read and display a verified public documentary film in the GuideDoc explorer. Use the numeric ID from current results or selected-film context. Preserve original titles. Pass current filters so subsequent recommendations retain them. Full films open on GuideDoc, with normal access requirements. Pass explorer_id from the active explorer context to update its view.

Input Schema

TableJSON Schema

Name	Required	Default
`id`	Yes
`filters`	No
`language`	No	en
`explorer_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`source`	No		GuideDoc public information only; full films require an eligible subscription and territory

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

addedInput schema / $defs

Added value: +{
+  "FilmFilters": {
+    "additionalProperties": false,
+    "properties": {
+      "country": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "description": "Country of production, not viewer location",
+        "title": "Country"
+      },
+      "director": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Director"
+      },
+      "festival": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Festival"
+      },
+      "genre": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Genre"
+      },
+      "max_duration_minutes": {
+        "anyOf": [
+          {
+            "maximum": 1000,
+            "minimum": 1,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Max Duration Minutes"
+      },
+      "scope": {
+        "default": "all",
+        "enum": [
+          "all",
+          "streaming",
+          "reference"
+        ],
+        "title": "Scope",
+        "type": "string"
+      },
+      "sort": {
+        "default": "relevance",
+        "enum": [
+          "relevance",
+          "newest",
+          "oldest",
+          "shortest"
+        ],
+        "title": "Sort",
+        "type": "string"
+      },
+      "spoken_language": {
+        "anyOf": [
+          {
+            "pattern": "^[a-z]{2,3}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Spoken Language"
+      },
+      "subtitle_language": {
+        "anyOf": [
+          {
+            "pattern": "^[a-z]{2,3}$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Subtitle Language"
+      },
+      "topic": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Topic"
+      },
+      "year_from": {
+        "anyOf": [
+          {
+            "maximum": 2200,
+            "minimum": 1800,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Year From"
+      },
+      "year_to": {
+        "anyOf": [
+          {
+            "maximum": 2200,
+            "minimum": 1800,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Year To"
+      }
+    },
+    "title": "FilmFilters",
+    "type": "object"
+  }
+}

addedInput schema / properties / explorer_id

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[0-9a-f]{32}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Explorer Id"
+}

addedInput schema / properties / filters

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/FilmFilters"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

changedInput schema / title

Previous value: -"get_documentaryArguments"New value: +"visual_get_documentaryArguments"

Changed2 schema fields changedSep 30, 2026
- addedInput schema / properties / language / const
```
Added value: +"en"
```
- removedInput schema / properties / language / enum
```
Removed value: -[
-  "en",
-  "ca",
-  "es"
-]
```
Changed1 schema field changedSep 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedSep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value beyond that: full films open externally on GuideDoc 'with normal access requirements,' original titles must be preserved, and passing explorer_id mutates the explorer view.

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 action, then layers usage and behavioral notes. Mostly efficient, though 'Preserve original titles' and the access-requirements sentence are slightly tangential to invoking the tool correctly.

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?

An output schema exists so return values needn't be described; the description covers purpose, ID sourcing, filter propagation and the explorer-view side effect, leaving nothing an agent needs to call it correctly.

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 description coverage is 0%, so the description must carry the load. It explains three of four params meaningfully (id source, filters retention purpose, explorer_id updating the active view); only the trivial const 'language' is left unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Read and display a verified public documentary film in the GuideDoc explorer.' It is clearly the single-film retrieval tool versus the search/list siblings, though it never names those alternatives (search_documentaries, catalogue_film) to sharpen the distinction.

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 concrete selection guidance: use the numeric ID from current results or selected-film context, and pass current filters so subsequent recommendations retain them. It stops short of stating exclusions or naming the sibling tools an agent should prefer for search scenarios.

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

All GuideDoc Documentary Database 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?