Tutorializer Video Tutorials

Show Tutorializer project overview

show_project_overview

Read-only

Render a bounded tenant-scoped Tutorializer project snapshot with tutorial, video, and voiceover counts. Use this after listing projects or when the user provides an immutable project id or stable public vanity id.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes	Tutorializer project id or stable public vanity id to render

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 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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a mild behavioral cue with 'snapshot' and 'bounded tenant-scoped', but it does not go into specifics about what the snapshot excludes or how counts are computed. No contradiction with 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?

Two sentences, each earning its place: the first states what the tool does, the second states when to use it. No filler or repetition of schema fields.

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?

The tool is simple (one required parameter), has an output schema, and annotations cover safety. The description gives enough to invoke it correctly. A minor gap is the missing explicit contrast with get_project for full-detail needs, but the count-snapshot framing makes the scope reasonably clear.

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% and the schema description already says 'Tutorializer project id or stable public vanity id to render'. The tool description reinforces this with 'immutable project id or stable public vanity id' but adds no new parameter-level semantics or formatting constraints. Baseline 3 is appropriate.

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?

The description names a concrete operation ('Render ... project snapshot') and pins down the content (tutorial, video, and voiceover counts), which clearly differentiates it from list_projects and get_project at the purpose level. 'Bounded tenant-scoped' adds a scope qualifier, though it is somewhat jargon-heavy and does not explicitly name sibling alternatives.

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?

The description gives clear invocation context: use after listing projects or when an immutable/stable id is already available. It does not explicitly state when not to use the tool or name get_project as the alternative for full project details, but the provided context is unambiguous enough for an agent to select it.

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?