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. Needs a signed-in Clipform account (an anonymous session is asked to sign in).

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Filter by tag name(s), comma-separated. AND logic: only forms with ALL tags are returned.
`sort`	No	Sort field (default: created_at)
`limit`	No	Number of forms to return (default 25, max 100)
`order`	No	Sort order (default: desc, newest first)
`cursor`	No	Pagination cursor from previous response's next_cursor
`search`	No	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.
`context`	Yes	Describe the user's underlying goal in one sentence - not the tool you're calling.
`published`	No	Filter by publish status
`workspace_id`	No	Workspace to act in (id from clipform_whoami workspaces). Omit to use the connection's default workspace.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`forms`	Yes	Matching forms (empty if none)
`next_cursor`	Yes	Pass as cursor to fetch the next page, or null when no more

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 6, 2026

addedInput schema / properties / workspace_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

addedOutput schema / properties / forms / items / properties / tags / items / properties / color / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
removedOutput schema / properties / forms / items / properties / tags / items / properties / color / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedOutput schema / properties / next_cursor / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / next_cursor / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / workspace_id

Added value: +{
+  "description": "Workspace to act in (id from clipform_whoami workspaces). Omit to use the connection's default workspace.",
+  "format": "uuid",
+  "type": "string"
+}

Changed5 schema fields changedAug 31, 2026

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"
+}

Changed1 schema field changedAug 29, 2026

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

Changed3 schema fields changedAug 20, 2026

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"
+]

Changed1 schema field changedJul 8, 2026

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"
+}

First observedJul 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavior: cursor-based pagination, next_cursor presence, and an authentication prerequisite. It does not cover rate limits or result size, but the added context is substantive.

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?

Four tight sentences with the core action front-loaded, followed by pagination and the search shortcut. Slight overlap between the pagination sentence and the schema's cursor description, but no real waste.

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, the description needn't explain return fields, and it sensibly limits itself to pagination mechanics and auth requirements. Coverage is adequate for a filtered-list tool with 9 documented parameters.

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% with rich per-parameter descriptions (tags AND logic, defaults, cursor source, search semantics), so the schema carries the parameter burden. The description echoes the search/cursor behavior rather than adding syntax or constraints beyond it.

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 and resource ('List forms in your workspace') plus scope ('optional filtering'), which is clearly distinct from the sibling clipform_get_form. It does not, however, explicitly name that sibling or otherwise route the agent between list and single-retrieve.

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 real usage direction: use search with part of a title instead of paging, and notes the signed-in-account requirement (anonymous sessions are asked to sign in). It stops short of stating when to prefer clipform_get_form over this list tool.

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

All Clipform 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.