campaignstack

campaignstack_send_gmail

Send an email via Gmail using a connected Google account. Requires a Google account to be connected and linked to the workspace. Use the Google integrations settings in the app to connect one first. If googleAccountId is omitted, uses the first connected Google account linked to the workspace. Returns the Gmail messageId and threadId on success. Provide htmlBody for rich formatting; body is used as the plain-text fallback. Optional attachments are passed as public URLs and downloaded server-side.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Recipient email address
`body`	Yes	Plain-text email body
`subject`	Yes	Email subject line
`htmlBody`	No	Optional HTML email body (used instead of body for rich formatting)
`attachments`	No	Up to 5 files to attach (18 MB total). Downloaded server-side into storage before sending.
`workspaceId`	No	Workspace ID (defaults to the bound workspace)
`googleAccountId`	No	Google account ID to send from. Defaults to the first connected Google account linked to the workspace.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes beyond the annotations by explaining the server-side download of attachments, the plain-text fallback behavior of body when htmlBody is provided, and the return of Gmail messageId/threadId on success. It also clearly signals the external side effect of sending an email, consistent with openWorldHint=true and readOnlyHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences with no wasted words. It front-loads the core action, then covers prerequisites, default behavior, return value, and attachment handling in a compact and logical order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description still explains what is returned on success. It covers prerequisites, default account selection, HTML/plain-text behavior, attachments limits and download semantics, making it complete enough for an agent to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful behavioral detail: body serves as the plain-text fallback to htmlBody, attachments are downloaded server-side, and the return value includes messageId/threadId. This supplements the schema descriptions without repeating them verbatim.

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 clearly states the tool sends an email via Gmail using a connected Google account, with a specific verb, resource, and channel. It distinguishes itself from sibling messaging tools like campaignstack_send_message and campaignstack_send_inmail by explicitly naming Gmail as the delivery mechanism.

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

Usage Guidelines4/5

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

The description provides clear context on prerequisites: a Google account must be connected and linked to the workspace, and it explains the default account selection behavior when googleAccountId is omitted. It does not explicitly name alternatives or state when not to use this tool versus send_message/send_inmail, but the Gmail-specific wording makes the intended use clear.

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

All campaignstack tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation3/5

Many tools share the same verb prefix (create_, list_, update_, get_) across closely related resources, so pairs like add_lead_to_external_list vs add_lead_to_sequence, create_signal_agent vs create_signal_watch, and approve_review vs approve_content_post can be confused. The descriptions are unusually detailed and cross-referenced, which mitigates but does not eliminate the ambiguity inherent in a 282-tool surface.

Naming Consistency4/5

Virtually every tool follows the campaignstack_verb_noun snake_case pattern, which is highly predictable. Minor deviations exist: destructive operations mix remove_ and delete_ (remove_lead_list vs delete_campaign), AI generation uses both craft_ and generate_, and the seo_/search_console_ subdomains introduce a second prefix convention.

Tool Count1/5

282 tools is an extreme mismatch by any reasonable standard, exceeding the 50+ threshold by more than 5x. Even for a full B2B outreach platform, this surface is far too large and would be better consolidated into higher-level operations or grouped sub-servers.

Completeness4/5

The tool surface is impressively comprehensive, covering campaigns, workflows, leads, content, ads, SEO, integrations, billing, and more with CRUD-level depth. Minor gaps remain: no single-ICP getter, no direct pause/delete for search watches, and no explicit delete for ad campaigns (only archive via update).

Resources

Need Help?