Skip to main content
Glama

get_automation

Read-only

Get one comment-to-DM automation: its platform (Instagram, the Facebook Page or X), its trigger, the DM text, the public replies, Follow first (Instagram), the follow-up (Instagram and Facebook), the limits and the counts (with the follow-ups sent and skipped).

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

Input Schema

NameRequiredDescriptionDefault
automation_idYesThe automation id (from list_automations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value by disclosing the returned surface in detail and flagging platform-conditional fields ('Follow first (Instagram)', 'follow-up (Instagram and Facebook)'), which tells an agent what will and will not be present; it stops short of mentioning not-found or permission behavior.

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?

A single front-loaded sentence opens with the verb and resource before the field list. The long comma chain with parenthetical platform qualifiers is slightly run-on but each clause carries information an agent needs about the payload.

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?

With no output schema, the burden of describing return values falls on the description, and it discharges that well by enumerating platforms, trigger, texts, follow-up settings, limits and counts. Only edge-case behavior (missing id, permissions) is unaddressed, which is minor for a read-only single-record fetch.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains automation_id and its origin. The description contributes nothing further about the identifier's format or validity, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one comment-to-DM automation') and then enumerates exactly what the single object contains (platform, trigger, DM text, replies, follow-ups, limits, counts). That field list strongly separates it from get_automation_activity and from list_automations, though the description never names a sibling to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use statement. Usage is only implied by 'Get one' plus the schema note that the id comes 'from list_automations', which suggests the list-then-fetch workflow but leaves it to inference.

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