Skip to main content
Glama

list_automations

Read-onlyIdempotent

List the DM and comment automations in a workspace, newest first.

Each entry carries its trigger (a comment keyword, a story reply, a DM keyword), whether it's currently active, which posts it targets, its DM/reply counts, and its id for get_automation / update_automation / delete_automation. The list is a summary: call get_automation for an automation's keywords, message text, buttons and AI brief.

stalled is set when an automation says "active" but is not firing (today: its Instagram connection expired) — relay its hint to the user rather than reporting the automation as healthy.

Read this before changing anything: an automation that already covers a keyword should be edited rather than duplicated, since two automations on the same trigger both fire.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "list_automations"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description still adds substantial behavior: newest-first ordering, what each entry contains, and the non-obvious `stalled` flag semantics with an instruction to relay `hint` instead of reporting health. That is exactly the kind of state an agent would otherwise misreport.

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?

Front-loaded with purpose and ordering, then detail routing, then the stalled caveat, then the mutation-avoidance rule. Each paragraph earns its place, though the field enumeration in the second sentence is slightly long for a tool that has an output schema.

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 read-only list tool with one parameter and an output schema, the description covers scope, ordering, entry contents, anomaly handling and the workflow constraint that motivates calling it. Nothing an agent needs to select or use it correctly is missing.

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 0% for the single `workspace_id` parameter, so the description would need to carry it. It implies workspace scoping ("in a workspace") but never states the expected identifier form or where to obtain it, even though a list_workspaces sibling exists. With one obvious parameter this is a minor but real gap.

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?

Opens with a specific verb and resource plus scope and ordering: "List the DM and comment automations in a workspace, newest first." It also distinguishes itself from the detail sibling by calling the list "a summary" and directing to get_automation for keywords, message text, buttons and AI brief.

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?

Gives explicit when-to-use routing (get_automation for full detail) and an explicit when-to-read-it-first rule: check this before creating, because an automation already covering a keyword should be edited rather than duplicated. It also warns that duplicate triggers both fire, which is a concrete reason to consult the list first.

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.

Resources