Skip to main content
Glama
Sign In

EmailFig

by com.emailfig
OverviewDiscussionsAdmin

Get automation report

get_automation_report
Read-onlyIdempotent

One automation's results: how many people entered, are in it, finished or left early and why, each step with who is waiting there and each email's results, and opens and clicks over the last 7 or 30 days.

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": {
      "id": "<id>"
    },
    "name": "get_automation_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe automation's id.
daysNoDays of opens and clicks: 7 or 30. Default 30.

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 already declare this a safe, idempotent, read-only operation, so the description's job is lighter. It adds real value by disclosing the scope of returned data — entry/exit counts, per-step waiters, per-email results, and a 7/30-day engagement window — though it omits response size, pagination, and any automation-state prerequisites.

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?

It is a single dense sentence, front-loaded with the resource, with each clause mapping to a distinct report section. Every clause earns its place, though a short structured list would scan faster for such a multi-part return value.

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 only two parameters, full schema coverage, and existing annotations, the main gap is the absent output schema — and the description compensates by describing the returned sections in detail. Remaining gaps around response size and format are minor for a read-only report tool.

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 already states that days controls 'Days of opens and clicks: 7 or 30. Default 30.' The description repeats that meaning ('opens and clicks over the last 7 or 30 days') but adds no syntax, format, or edge-case detail beyond the schema, so the 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?

The description names a specific resource ('One automation's results') and enumerates the exact report contents, so an agent knows precisely what it retrieves. It stops short of explicitly differentiating itself from the sibling get_campaign_report, so it is clear but not sibling-disambiguating.

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: call this to get results for a single automation, identified by id. There is no explicit when-to-use guidance, no exclusions, and no pointer to alternatives such as get_campaign_report for campaign-level data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EmailFig toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources