Skip to main content
Glama

uplika

by com.uplika
OverviewDiscussionsAdmin

List automations

list_automations
Read-only

Automations on the connected accounts: name, channel, whether it is live or a draft, triggers, run count, and templateParams when the flow still has its template shape. Filter by accountId, status (draft or live) or templateId. Use get_automation to read one flow's document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNodraft = not enabled, live = enabled.
accountIdNoOnly automations on this connected account.
templateIdNoOnly automations made from this template (list_automation_templates).
workspaceIdNoWhich workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / accountId
      Added value: +{
+  "description": "Only automations on this connected account.",
+  "type": "string"
+}
    • addedInput schema / properties / status
      Added value: +{
+  "description": "draft = not enabled, live = enabled.",
+  "enum": [
+    "draft",
+    "live"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / templateId
      Added value: +{
+  "description": "Only automations made from this template (list_automation_templates).",
+  "type": "string"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint, non-destructive). The description adds field-level return context and a conditional note that templateParams appears only when the flow still has its template shape. It doesn't cover pagination or volume limits, but the added behavioral detail is meaningful.

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 dense sentences: return content, filters, then alternative tool. No wasted words and the key information is front-loaded.

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 read-only list tool with no output schema, the description tells the agent what is returned and how to filter, plus the sibling for detail. Missing only pagination/ordering behavior, which is minor.

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?

Schema coverage is 100%, so the schema already documents each parameter with descriptions and an enum. The description maps the filters to intent and hints at availability of templateParams, adding marginal value.

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 specific verb (list) plus resource (automations) and enumerates the returned fields: name, channel, live/draft, triggers, run count, templateParams. This clearly distinguishes it from get_automation, which reads a single flow's document.

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 names the alternative (get_automation) and its purpose, and specifies the three filter dimensions (accountId, status, templateId). The routing rule is clear.

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

All uplika toolsInspect
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