Skip to main content
Glama

get_automation

Read-onlyIdempotent

Read one automation in full: trigger (keywords, match mode, target posts), the public-reply and DM text, buttons, follow gate, AI brief, and its counters (DMs sent and failed, replies received, taps, AI usage) and stalled flag.

This is the only way to see what an automation currently says — the list_automations result is a summary. Call it before update_automation so an edit merges onto what is really there, and to answer "what does my 'price' keyword reply with?" or "is this automation actually working?".

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>",
      "automation_id": "<automation_id>"
    },
    "name": "get_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes
automation_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
statsNoWhat happened after this automation ran. `dms_failed` is a send that was tried and did not land (dead token, Meta rate limit, policy rejection) — read it next to `events_received` before concluding an automation 'works'.
statusYes
ai_goalYes
ai_linkYes
ai_toneYes
stalledNo
dms_sentYes
keywordsYes
post_idsYes
ai_contextYes
dm_buttonsNo
post_targetYes
ice_breakersYes
trigger_typeYes
keyword_matchYes
ask_for_followYes
ai_exit_conditionYes
follow_up_enabledNo
follow_up_messageNo
dm_link_button_urlYes
follow_gate_messageYes
ice_breaker_repliesNo
private_dm_messagesYes
public_replies_sentYes
dm_link_button_labelYes
public_reply_messagesYes
follow_up_delay_secondsNo
ice_breakers_sync_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered; the description adds the important behavioral fact that the list endpoint returns only a summary and that edits must be based on this full read to avoid merging on stale data. The field inventory is partially redundant with the output schema, which keeps it from a 5.

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 short sentences: what it returns, why it is uniquely necessary, and when to call it. The payoff ("only way to see what an automation currently says") is front-loaded and every sentence carries load.

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 tool with an output schema, the return-value burden is light, and the description covers purpose, uniqueness versus the list tool, and the key workflow dependency on `update_automation`. The only real hole is identifiers/parameters, and the interaction with sibling tools like `get_automation_logs` for the "is it working?" question is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description never mentions `workspace_id` or `automation_id`, and schema description coverage is 0%, so neither field is documented anywhere. The parameter names are largely self-explanatory ID strings, which prevents a 1, but the description does not compensate for the coverage gap or clarify scoping/identifier format.

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 scope ("Read one automation in full") and enumerates exactly what is included: trigger keywords/match mode/target posts, reply and DM text, buttons, follow gate, AI brief, counters, and the `stalled` flag. It also explicitly contrasts itself with `list_automations`, so an agent can distinguish the two without opening a 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 when-to-use guidance with a prerequisite ordering ("Call it before update_automation so an edit merges onto what is really there") and two real user questions it answers. It also names the alternative (`list_automations` is only a summary), which is exactly the routing information an agent needs.

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