process_campaigns
Process all due campaign schedules (includeFailed: true to retry failed ones)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| includeFailed | No | Also retry failed schedules |
Mailcannon
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully convey behavioral traits. It states it processes due schedules but does not explain what 'process' entails (e.g., sending emails, mutating state, side effects), leaving significant ambiguity for an AI agent.
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?
The description is very concise with a single sentence, but its brevity sacrifices clarity on usage and behavior, preventing a higher score.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool likely performs actions (processing campaigns) and lacks an output schema, the description fails to explain return values, side effects, or prerequisites, making it incomplete for reliable agent invocation.
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?
With 100% schema description coverage for the only parameter, the description's mention of includeFailed adds no new meaning beyond the schema's description, meeting the baseline but not exceeding it.
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?
The description specifies the verb 'process' and the resource 'campaign schedules', and distinguishes the tool's action of processing due schedules from sibling tools like pause/resume/retry_failed by noting the option to retry failed ones.
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?
The description implies usage for processing due campaign schedules and mentions the includeFailed parameter for retrying failed ones, but does not explicitly compare with sibling tools like 'retry_failed' or provide conditions when not to use this tool.
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.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct action and resource. Campaign lifecycle steps (create, update, delete, schedule, pause, resume) are clearly separate from contact management (add, remove, update tags) and provider/domain operations. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with underscores (e.g., add_contact, check_domain_deliverability, delete_campaign_step). Mixing of singular/plural nouns (list_campaigns vs list_tags) is intentional and does not break consistency.
Tool Count4/5
34 tools is high but justified for a full-featured email campaign server covering campaigns, contacts, providers, scheduling, deliverability, and task management. A few tools like check_email_spam_score and check_step_spam_score could be merged, but overall the count is reasonable.
Completeness5/5
The tool surface covers the complete CRM lifecycle: campaign CRUD, step management, contact CRUD with tags, provider setup, scheduling, deliverability checks, and spam analysis. Only minor gaps like per-campaign analytics or import/export exist, but core workflows are fully covered.