Skip to main content
Glama

List automations

list_automations
Read-onlyIdempotent

Use this when the founder asks which automations a project has, what triggers them and whether they are live, or where a particular contact is in one. It returns every automation with its trigger, live status and delivery counters (enrolled, completed, sent, delivered, bounced). Pass a contact handle and each automation also reports that contact's own enrollment: state, a human label for the step they are on right now, and when a waiting step resumes. Not for one-off emails to the list (see list_broadcasts).

Read-only. There is no tool to enroll a contact in an automation: every enrollment traces back to a real event (a signup, a verification, a referral, a stage change, a survey answer), never a direct write.

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": {
      "project": "<project>"
    },
    "name": "list_automations"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactNoA contact handle, like `con_…`. When given, each automation includes this contact's own enrollment state.
projectYesThe project handle, like `prj_…`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantive context: the exact return payload per automation, the extra per-contact enrollment block (state, human step label, resume time), and the provenance rule that every enrollment traces to a real event rather than a direct write. That provenance note is behavioral information no annotation or schema field conveys.

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?

Front-loaded with the usage trigger and the returned fields, then the optional-parameter behavior, then the exclusion and the read-only/enrollment caveat. Each sentence carries distinct information; the counter list is dense but functional rather than filler.

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?

With no output schema, the description takes on the return-value burden and discharges it by enumerating the per-automation fields and the conditional per-contact block. Only two parameters exist and both are covered, so nothing an agent needs in order 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?

Schema coverage is 100%, so baseline is 3; the description earns above that by explaining what `contact` actually changes in the response — enrollment state, a human-readable current step, and when a waiting step resumes — rather than just restating the schema's one-line gloss. `project` is left as the obvious scope handle, which is adequate.

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?

Names a specific verb+resource ('list automations') and immediately says what each record carries: trigger, live status, and delivery counters (enrolled, completed, sent, delivered, bounced). It also explicitly separates itself from `list_broadcasts`, so an agent can route without opening either schema.

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 concrete triggering situations ('when the founder asks which automations a project has, what triggers them and whether they are live, or where a particular contact is in one') plus an explicit exclusion pointing at the alternative ('Not for one-off emails to the list — see `list_broadcasts`'). It further closes a likely dead end by stating no tool enrolls a contact, which prevents a false search for one.

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.