Jabbertoon cartoon studio

List Jabbertoon's ready-made cartoon moves

list_moves

Read-only

Lists the ready-made moves a character can do (walk in, wave hello, hop, bow, slump, talk...): id, name, length in seconds, the bodies it works on (two legs, four, none), its settings with units, page and links. A does block plays one: {"op": "does", "who": "dog", "behaviour": "c4c:beh:wave_hello"}. q keeps the moves whose words match or that do what a word means (dance finds Groove, scared finds Cower). Example: {"q": "wave"}.

Input Schema

Name	Required	Description	Default
`q`	No	Words to look for ("wave", "dance"); leave it out for every move.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / q / description

Previous value: -"Words to look for in a move's name, id or description, or what the move does, e.g. \"wave\", \"walk in\" or \"dance\". Leave it out to list every move."New value: +"Words to look for (\"wave\", \"dance\"); leave it out for every move."

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "problem": {
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "fix": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "says": {
-          "type": "string"
-        },
-        "where": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "code",
-        "where",
-        "says",
-        "fix"
-      ],
-      "type": "object"
-    }
-  },
-  "properties": {
-    "count": {
-      "description": "How many moves are listed here.",
-      "type": "integer"
-    },
-    "error": {
-      "$ref": "#/$defs/problem"
-    },
-    "filters": {
-      "description": "The filters this answer used, exactly as given.",
-      "type": "object"
-    },
-    "moves": {
-      "items": {
-        "properties": {
-          "description": {
-            "type": "string"
-          },
-          "id": {
-            "description": "The pack id, e.g. c4c:beh:wave_hello.",
-            "type": "string"
-          },
-          "license": {
-            "type": "string"
-          },
-          "links": {
-            "description": "Links that open the move: blocks (the block editor) and studio (the cartoon studio).",
-            "type": "object"
-          },
-          "name": {
-            "type": "string"
-          },
-          "pack_slug": {
-            "description": "The short name used in #p= links, e.g. wave_hello.",
-            "type": "string"
-          },
-          "seconds": {
-            "description": "How long the move's preview plays, in seconds.",
-            "type": [
-              "number",
-              "null"
-            ]
-          },
-          "skeleton": {
-            "description": "True for the moves that bend chains, reach with hands or turn between views.",
-            "type": "boolean"
-          },
-          "slug": {
-            "description": "The last part of the move's page URL.",
-            "type": "string"
-          },
-          "url": {
-            "description": "The move's page on jabbertoon.com.",
-            "type": "string"
-          },
-          "version": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "slug",
-          "name",
-          "url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "notes": {
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "ok": {
-      "type": "boolean"
-    },
-    "total": {
-      "description": "How many moves there are in all.",
-      "type": "integer"
-    },
-    "url": {
-      "description": "The page that lists every move.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "ok",
-    "url"
-  ],
-  "type": "object"
-}New value: +null

First observedOct 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the full shape of returned records, the fuzzy/semantic nature of q matching, and how the result is consumed in a does block. It omits pagination or ordering behavior, but for a safe read tool this is solid added context.

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-loaded with the resource and returned fields, followed by search semantics and a compact example. The embedded does-block JSON is slightly tangential to a listing tool, but it is short and directly illustrates why the ids returned here matter.

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 no output schema, the description carries the return-shape burden and does so by enumerating every field, including units on settings. Combined with the search semantics explanation, an agent has enough to invoke and interpret the result; only ordering/pagination detail is absent.

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 coverage is 100% and the q parameter is already documented, so the baseline is 3. The description goes further by explaining that q matches words OR meaning ("dance finds Groove, scared finds Cower") and gives a concrete example, adding semantics the schema does not carry.

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 (Lists) and resource (ready-made cartoon moves) and enumerates the returned fields (id, name, length, bodies, settings, page, links). It is clearly distinct from list_characters and list_looks by resource, though it never explicitly contrasts itself with the singular get_move sibling.

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 clear usage context: omit q for every move, use q for word/meaning search, and shows how a returned move is played via a does block. It stops short of naming an alternative tool (e.g. get_move) for retrieving a single move, so it is context-rich but not a full when/when-not routing guide.

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

All Jabbertoon cartoon studio 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?