Skip to main content
Glama

get_automation_logs

Read-onlyIdempotent

The activity log of one automation: each time it fired, newest first — when, for which kind of trigger, what it sent, whether the person wrote back, why a follow-up did not go out, and why a send failed.

Use it to answer "did my automation actually run on that reel?", "who replied?", "why didn't the follow-up send?" and "why didn't they get the DM?" (failures[].message is written for the user — relay it as-is). Page with skip (limit up to 200). An empty list means the automation has not fired yet — check get_automation's stalled flag and counters before assuming it is broken.

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_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
workspace_idYes
automation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive), but the description adds ordering (newest first), pagination mechanics (skip, limit up to 200), and the crucial semantic that an empty list means "not fired yet" rather than failure. It also tells the agent `failures[].message` is user-facing prose to relay verbatim, which is behavioral guidance no annotation could convey.

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 resource definition, then use cases, then operational caveats (paging, empty-list interpretation). The long opening sentence is dense but every clause maps to a distinct returned field; no sentence is filler and the operator-critical caveat is placed last where it is most memorable.

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?

Output schema exists, so field-by-field return documentation is unnecessary; the description instead covers what the schema cannot — ordering, paging bounds, failure-message relaying, and empty-result diagnosis. For a read-only, four-parameter log tool, an agent has everything needed to call it and interpret the result correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It does add real detail for `limit` (max 200) and implies `skip`-based paging, but it never mentions the defaults (skip=0, limit=50) or states what `workspace_id` and `automation_id` scope to. Partial compensation for a fully undocumented schema.

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 a specific verb and resource (activity log of one automation) and immediately enumerates what a row contains: fire time, trigger kind, payload sent, reply status, follow-up suppression reason, and failure reason. This is clearly distinguishable from get_automation, which the description positions as the source of `stalled` status and counters rather than per-fire history.

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 trigger questions the tool answers ("did my automation actually run on that reel?", "who replied?", "why didn't the follow-up send?"), plus explicit guidance on the empty-result case: check get_automation's `stalled` flag and counters before assuming breakage. That is a when-to-use rule, an interpretation rule, and an alternative-source pointer in one place.

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