Skip to main content
Glama
chzkyy
by chzkyy

list_recipes

List recipes for the authenticated Workato user. Filter by folder, adapters, running status, or date range, with paginated results and optional code exclusion for faster retrieval.

Instructions

List recipes belonging to the authenticated user (GET /api/recipes). Supports filtering by folder, adapters (connectors), running status, and date range. Results are paginated (default: per_page=100, max 100). Set exclude_code=true to speed up listing for large accounts.

Note: The Workato API does NOT support server-side name search. To find recipes by name, use the search_recipes tool instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
orderNoSort order (default: 'default')
runningNoIf true, return only running recipes
per_pageNo
since_idNoReturn recipes with IDs lower than this value
folder_idNoFolder/project id to list recipes from
exclude_codeNoExclude recipe code from response (faster for large lists)
stopped_afterNoISO 8601 datetime — only recipes stopped after this
updated_afterNoISO 8601 datetime — only recipes updated after this
with_subfoldersNoInclude recipes from subfolders (default: false)
adapter_names_allNoComma-separated adapter names — recipes must use ALL of them
adapter_names_anyNoComma-separated adapter names — recipes must use at least ONE
Install Server

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden. It discloses pagination defaults (per_page=100, max 100), the performance impact of exclude_code, and the API's lack of name-search support. It does not mention rate limits or error behavior, but the disclosed details are substantive and useful.

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?

Two clearly separated paragraphs: the first describes the tool's core behavior and key options, the second provides an important routing note. Every sentence adds information without redundancy or padding.

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?

For a complex, 12-parameter tool with no output schema, the description covers essential invocation details: scope, filters, pagination, performance optimization, and when to prefer a sibling. Nothing critical that an agent needs to call this correctly is missing.

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?

With 83% schema coverage, the description adds value beyond the schema by summarizing the filter dimensions (folder, adapters, running status, date range) and highlighting the performance tradeoff of exclude_code. It also states default pagination values, which the schema does not fully convey.

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?

The description clearly states the tool lists recipes for the authenticated user via a specific endpoint, and explicitly contrasts it with search_recipes for name-based lookup. This distinguishes it from siblings and leaves no ambiguity about its function.

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

Usage Guidelines5/5

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

Explicitly instructs when to use search_recipes instead (when searching by name) because the API does not support server-side name search. This provides clear routing guidance relative to an alternative tool.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chzkyy/mcp_workato'

If you have feedback or need assistance with the MCP directory API, please join our Discord server