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

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds valuable behavioral context: results are paginated with a cursor, next_cursor appears when more results exist, and the operation is scoped to the workspace. 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?

Three sentences, no filler. The main purpose comes first, followed by pagination behavior and a targeted search tip. Every sentence earns its place.

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?

For a list endpoint with 8 well-documented parameters, a useful output schema, and safety annotations, the description covers the essential behavioral notes (pagination, search shortcut). It does not explicitly mention when to use get_form instead, but the 'list' identity makes that largely unnecessary. Slight room for more explicit sibling differentiation.

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%, so the baseline is 3. The description adds meaning around search and cursor usage ('instead of paging through results'), but the schema already documents all parameters thoroughly. This is adequate without duplicating schema details.

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: 'List forms in your workspace with optional filtering.' The workspace scope differentiates it from sibling list tools (list_assets, list_compositions) and the singular clipform_get_form. The name and description align unambiguously.

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 internal guidance: use the search parameter to find a form by name instead of paging through results, and explains cursor-based pagination. It does not explicitly contrast with clipform_get_form for retrieving a known form by ID, but the search-focused advice covers the main alternative scenario.

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

A3.9/5.0
Disambiguation3/5

Most form/node CRUD tools are clearly distinct, but the render/generate trio (generate_video, render_video_template, render_composition) and get_responses vs get_results can be confused by name alone. The descriptions include strong disambiguation guidance, so the overlap is manageable but still present.

Naming Consistency4/5

The vast majority of tools follow a consistent clipform_verb_noun snake_case pattern, with create/get/update/delete/list used predictably. Minor deviations include get_more_tools lacking the clipform_ prefix and whoami not matching the verb_noun convention.

Tool Count2/5

At 34 tools, this is above the range where a toolset feels well-scoped, and several entries are auxiliary or internal (whoami, log_generation, get_more_tools, search_news). The domain is broad, but the surface could be consolidated without losing core capabilities.

Completeness4/5

The set covers form and node lifecycle, media upload/attachment, logic wiring, publishing, responses/results, and content generation (TTS, video, music, stock media). Minor gaps remain, such as no conditional branching in set_logic and no general media-library listing tool.

Resources