Skip to main content
Glama

Get automation stats

get_stats
Read-only

How automations are doing: comments, people who got a DM, got the link, clicked it, shared their email, and per day for the last 14 days.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
automation_idNoAutomation id from list_automations. Left out: the whole account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by disclosing what data comes back (five funnel metrics) and that the window is fixed at the last 14 days with per-day breakdown. That time-window constraint is real behavioral context an agent cannot get from annotations. It still says nothing about aggregation semantics (unique vs total people) or response shape, but it clears the bar above the annotation baseline.

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?

One compact sentence that front-loads the purpose and then lists metrics efficiently. The colloquial opener 'How automations are doing' is the only low-value phrasing, and it is short enough not to waste much.

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 description carries the burden of describing returns, and it does so by enumerating the metrics plus the 14-day per-day window. For a one-optional-parameter read tool with readOnlyHint set, this is nearly complete; only aggregation semantics and response format remain unstated.

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 100% and the schema description already explains the automation_id and the omit-for-whole-account behavior, so the description adds nothing on parameters. The plural 'automations' phrasing in the description arguably works against the schema, which clarifies a single id or the whole account.

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?

The description names the resource (automation stats) and enumerates the actual metrics returned — comments, DMs sent, link delivered, clicks, emails shared — which lets an agent separate it from get_automation or list_automations. The wording 'How automations are doing' is informal and slightly obscures that this is a metrics-retrieval call, and the plural 'automations' is a mild mismatch with the single automation_id parameter.

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?

Usage is implied rather than stated: an agent can infer this is the tool for performance numbers as opposed to configuration. There is no explicit 'use this when…' or any exclusion telling the agent when get_automation is the better call, so the routing is left 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