Tilebox

List public workflows

list_public_workflows

Read-only

List publicly shared Tilebox workflow summaries. Pass the returned reference to get_workflow to retrieve releases. Follow next_cursor for additional pages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_public_workflows"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	maximum workflows per page; default and maximum 100
`cursor`	No	next_cursor from the previous response

Output Schema

Name	Required	Description	Default
`workflows`	Yes	list of workflows
`next_cursor`	No	cursor for the next page; absent on the final page

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 30, 2026

addedOutput schema / properties / workflows / items / properties / id

Added value: +{
+  "description": "stable workflow UUID used to scope task identifiers",
+  "type": "string"
+}

addedOutput schema / properties / workflows / items / properties / legacy_task_aliases

Added value: +{
+  "description": "whether the workflow also exposes legacy unscoped task aliases; omitted when unknown",
+  "type": [
+    "null",
+    "boolean"
+  ]
+}

addedOutput schema / properties / workflows / items / properties / project_slug

Added value: +{
+  "description": "portable, non-unique project slug",
+  "type": "string"
+}

addedOutput schema / properties / workflows / items / properties / reference

Added value: +{
+  "description": "remote workflow address; use this value for reference and workflow_reference arguments",
+  "type": "string"
+}

added

Output schema / properties / workflows / items / properties / releases / items / properties / content / properties / build_config

Added value: +{
+  "additionalProperties": false,
+  "description": "build rules for this release; absent when unknown",
+  "properties": {
+    "exclude": {
+      "description": "file patterns to exclude, relative to the build root",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "include": {
+      "description": "file patterns to include, relative to the build root",
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "use_gitignore": {
+      "description": "whether to apply Git ignore rules; defaults to true when omitted",
+      "type": [
+        "null",
+        "boolean"
+      ]
+    }
+  },
+  "required": [
+    "include",
+    "exclude"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

changed

Output schema / properties / workflows / items / properties / releases / items / properties / content / properties / tasks / description

Previous value: -"task identifiers included in the release content"New value: +"unbound task definitions; scope is supplied by the runner, not the release content"

removedOutput schema / properties / workflows / items / properties / slug

Removed value: -{
-  "description": "workflow slug in your own namespace, or namespace:slug for shared workflows from other namespaces",
-  "type": "string"
-}

changedOutput schema / properties / workflows / items / required

Previous value: -[
-  "slug",
-  "name",
-  "summary",
-  "description",
-  "releases"
-]New value: +[
+  "id",
+  "project_slug",
+  "reference",
+  "name",
+  "summary",
+  "description",
+  "releases"
+]

Changed2 schema fields changedOct 12, 2026

addedOutput schema / properties / workflows / items / properties / summary

Added value: +{
+  "description": "short text summary of the workflow",
+  "type": "string"
+}

changedOutput schema / properties / workflows / items / required

Previous value: -[
-  "slug",
-  "name",
-  "description",
-  "releases"
-]New value: +[
+  "slug",
+  "name",
+  "summary",
+  "description",
+  "releases"
+]

First observedOct 1, 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, so the safety profile is covered. The description adds genuinely useful behavior: results are summaries only, releases require a follow-up get_workflow call, and results are paginated via next_cursor.

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 short sentences with zero filler; the core purpose is front-loaded and each remaining sentence carries an actionable instruction (follow-up call, pagination).

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 and full parameter documentation, the description covers what an agent needs: what it lists, how to page, and how to drill into releases. Minor gap is that 'publicly shared' is not clarified (any auth or ownership implications).

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 both parameters are fully documented in the schema, so the baseline is 3. The description reinforces cursor usage ('Follow next_cursor for additional pages') but adds nothing about the limit parameter or its max-100 cap beyond what the schema already states.

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 with scope: 'List publicly shared Tilebox workflow summaries.' The 'publicly shared' qualifier implicitly separates it from the sibling list_workflows, though the contrast is never made explicit.

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?

'Pass the returned reference to get_workflow to retrieve releases' gives clear next-step routing for the follow-up call, and 'Follow next_cursor for additional pages' covers pagination. It does not, however, say when to prefer this over list_workflows or state any exclusions.

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

All Tilebox 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?