Tutorializer Video Tutorials

Show project overview

show_project_overview

Read-only

Use this when someone wants a quick visual overview of one Tutorializer project. Returns a card with the project's name, domain and logo, how many tutorials, videos and voiceover lines it has (counted up to 100 each) and its 8 most recently edited tutorials. Not for missing languages or devices.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes	Project id or its stable public vanity id

Output Schema

TableJSON Schema

Name	Required	Description	Default
`project`	Yes
`tutorials`	Yes
`videoCount`	Yes
`speechCount`	Yes
`tutorialCount`	Yes
`videoCountIsLowerBound`	Yes
`speechCountIsLowerBound`	Yes
`tutorialCountIsLowerBound`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

changedInput schema / properties / projectId / description

Previous value: -"Tutorializer project id or stable public vanity id to render"New value: +"Project id or its stable public vanity id"

Changed1 schema field changedSep 20, 2026

changedOutput schema / properties / project / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "domain": {
-        "anyOf": [
-          {
-            "maxLength": 253,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "maxLength": 200,
-        "minLength": 1,
-        "type": "string"
-      },
-      "name": {
-        "maxLength": 200,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "domain"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "domain": {
+        "anyOf": [
+          {
+            "maxLength": 253,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "logo": {
+        "anyOf": [
+          {
+            "maxLength": 2048,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "name": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "domain",
+      "logo"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedSep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, closed world), and the description adds real behavioral detail beyond that: counts are capped at 100 each and only the 8 most recently edited tutorials are returned. Those truncation limits are the kind of nuance an agent needs and are not implied by annotations.

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?

Three tight sentences, front-loaded with the usage trigger, then the return shape, then the exclusion. Every clause carries information; no filler or restatement of the tool name.

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, return values need not be re-explained, and the description still surfaces the count caps and the 8-item tutorial limit. Minor gap: it does not indicate where to go for the full tutorial list or full counts (e.g. list_tutorials) once those truncations apply.

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 description coverage is 100% and the single parameter ('Project id or its stable public vanity id') is fully documented in the schema. The description adds no syntax, format, or lookup guidance beyond 'one Tutorializer project', so baseline 3 applies.

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 and resource ('quick visual overview of one Tutorializer project') and then enumerates exactly what the overview contains (name, domain, logo, counts, 8 most recently edited tutorials). The closing exclusion ('Not for missing languages or devices') implicitly separates it from get_project_localization_summary, so an agent can route without opening other schemas.

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 a clear trigger ('Use this when someone wants a quick visual overview of one project') plus an explicit exclusion for languages/devices. It does not name a sibling alternative (e.g. get_project for full detail or list_tutorials for the complete tutorial list), so the when-not guidance is partial rather than complete.

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

All Tutorializer Video Tutorials 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?