Skip to main content
Glama

List saved workflows

writ_list_workflows
Read-onlyIdempotent

Lists the workflows saved in the Writ account; each runs on demand without live browsing. Returns id, name, declared inputs (with input_rules: the values and format an input accepts), schedule, whether it is pinned as its own run_ tool, and, for an API with several functions, their names (functions, write_functions): call one with function_name.

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": "writ_list_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoName/description filter, e.g. a site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Optional name/description filter."New value: +"Name/description filter, e.g. a site."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuinely new context: saved workflows run on demand without live browsing, and it enumerates what the response contains (id, name, input_rules, schedule, pinned status, function lists), which is valuable given there is no output schema.

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?

One dense sentence, front-loaded with the core action and followed by the return-shape detail. It is long but every clause carries information; only the trailing 'call one with function_name' instruction is slightly out of place in a listing description.

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 one-parameter read tool with no output schema, the description covers the important ground by describing the returned fields and the meaning of input_rules. It omits any mention of the search filter and of ordering or volume of results, which keeps it short of fully complete.

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?

With a single optional parameter at 100% schema description coverage, the schema already explains that 'search' filters by name/description. The description does not mention the search parameter at all, so it adds no meaning beyond the schema; baseline 3 applies.

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: lists workflows saved in the Writ account. It also adds distinguishing detail (pinned workflows appear as their own run_<name> tool, multi-function APIs expose function_name), but it never names a sibling tool such as writ_run_workflow, so the boundary with alternatives is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the discovery step before running a workflow, and 'call one with function_name' hints at the follow-up action. There is no explicit when-to-use/when-not-to-use guidance and no named alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.