Skip to main content
Glama

Clipform

by io.github.Clipform

List Clipforms

clipform_list_forms
Read-onlyIdempotent

List forms in your workspace with optional filtering. Returns paginated results (cursor-based). next_cursor is included when more results exist. To find or open a form by name, pass search with part of its title instead of paging through results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by tag name(s), comma-separated. AND logic: only forms with ALL tags are returned.
sortNoSort field (default: created_at)
limitNoNumber of forms to return (default 25, max 100)
orderNoSort order (default: desc, newest first)
cursorNoPagination cursor from previous response's next_cursor
searchNoFilter to forms whose title contains this text (case-insensitive substring). Use this to resolve a form by name in one call instead of paginating.
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.
publishedNoFilter by publish status

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formsYesMatching forms (empty if none)
next_cursorYesPass as cursor to fetch the next page, or null when no more

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "context"
+]
    • addedOutput schema / properties / forms / items / properties / builder_url
      Added value: +{
+  "description": "Dashboard Build tab for this form. Not present for an anonymous caller.",
+  "type": "string"
+}
    • addedOutput schema / properties / forms / items / properties / viewer_url
      Added value: +{
+  "description": "Live respondent link. Only present for a published (is_live) form, and not for an anonymous caller.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Search forms by title (case-insensitive substring match)"New value: +"Filter to forms whose title contains this text (case-insensitive substring). Use this to resolve a form by name in one call instead of paginating."
  3. Changed3 schema fields changed
    • removedOutput schema / properties / forms / items / properties / created_at
      Removed value: -{
-  "type": "string"
-}
    • removedOutput schema / properties / forms / items / properties / updated_at
      Removed value: -{
-  "type": "string"
-}
    • changedOutput schema / properties / forms / items / required
      Previous value: -[
-  "id",
-  "title",
-  "share_id",
-  "is_live",
-  "has_unpublished_changes",
-  "created_at",
-  "updated_at",
-  "tags"
-]New value: +[
+  "id",
+  "title",
+  "share_id",
+  "is_live",
+  "has_unpublished_changes",
+  "tags"
+]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "forms": {
+      "description": "Matching forms (empty if none)",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "has_unpublished_changes": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_live": {
+            "type": "boolean"
+          },
+          "share_id": {
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "color": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "id",
+                "name",
+                "color"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "share_id",
+          "is_live",
+          "has_unpublished_changes",
+          "created_at",
+          "updated_at",
+          "tags"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass as cursor to fetch the next page, or null when no more",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "forms",
+    "next_cursor"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's burden is light. It adds genuinely useful behavior: results are cursor-based paginated, and next_cursor appears when more results exist. This tells the agent how to iterate and when to stop.

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 compact sentences, each with a distinct job: core action, pagination behavior, and search guidance. No redundant filler, and the most important information is front-loaded.

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?

Even with 8 parameters, the schema fully documents each one, and an output schema exists. The description covers the key behavioral aspects not in the schema—cursor-based pagination and the search shortcut—so an agent has everything needed 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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema. It frames the search parameter as the way to resolve a form by name in one call, and explains the cursor/pagination flow. This contextual guidance is not present in the individual parameter descriptions.

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 'List' and resource 'forms in your workspace' with optional filtering. Clearly distinguishes itself from single-form retrieval siblings like clipform_get_form by emphasizing a list operation. The description immediately conveys what the tool does.

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?

Provides clear context for when to use the search parameter instead of paginating to find a form by name. This guides the agent's strategy within the tool. It does not explicitly exclude alternatives like clipform_get_form, but the intended use case is well implied.

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

All Clipform toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: form CRUD, node management, media upload/attach, rendering, search, and guidance retrieval are all separable. The main overlap is among the three render tools (clipform_generate_video, clipform_render_video_template, clipform_render_composition), but their descriptions include explicit disambiguation guidance, so an agent can correctly choose. clipform_get_guide and clipform_get_workflow are also similar but clearly differentiated.

Naming Consistency4/5

Tool names follow a consistent clipform_<verb>_<noun> pattern throughout, e.g., clipform_create_form, clipform_add_node, clipform_update_node, clipform_delete_node. Minor deviations exist: clipform_whoami is not verb_noun, and get_more_tools lacks the clipform_ prefix, but these are edge cases and the overall convention is highly predictable.

Tool Count3/5

34 tools is on the heavy side for a single MCP server. The server covers a broad domain (form creation, node editing, media management, video rendering, TTS, search, guidance, imports, responses), so the count is defensible, but it is above the typical well-scoped range and may add navigation overhead.

Completeness5/5

The tool surface covers the full lifecycle: create/read/update/delete forms and nodes, media upload/attach/delete, multiple render paths with status checking, TTS generation, music/image/video search, form import, response retrieval, and workflow/guide knowledge. The main gap is lack of a direct branching-logic editor (option-based branching is only in the dashboard), but the API consciously documents that limitation and the rest of the lifecycle is complete.

Resources