Skip to main content
Glama
Sign In

EmailFig

by com.emailfig
OverviewDiscussionsAdmin

List campaigns

list_campaigns
Read-onlyIdempotent

Recent campaigns, newest first, with status and headline stats. Returns up to 25.

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": "list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Default 10.
statusNoOnly campaigns in this status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: newest-first ordering and a 25-item cap on returns. It does not mention pagination, what happens when more than 25 exist, or how 'headline stats' are shaped.

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?

Two short sentences with zero filler, and the sort order and cap are front-loaded. It is arguably too terse for the scope, but no sentence is wasted.

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 simple, read-only, two-parameter list tool with complete schema documentation and no output schema, this is nearly enough. The remaining gap is return-value detail, specifically whether the 25 cap implies truncation and what the 'headline stats' fields contain.

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 100%, so both limit and status are fully documented including the enum values and the default of 10. The description's 'Returns up to 25' reinforces the limit maximum but adds no new meaning beyond the schema's maximum constraint.

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 resource and scope: recent campaigns, sorted newest first, with status and headline stats. An agent can tell it apart from singular siblings like get_campaign, though the description never uses an explicit verb like 'list' and relies on the title for that framing.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. It doesn't say to use this for browsing versus get_campaign for a single record, or get_campaign_report for metrics, so the agent must infer the choice from sibling names alone.

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