rankparse-mcp

outreach_sending_status

Read-onlyIdempotent

Get the Gmail sending status of one mailbox (the workspace default, or the one named by mailbox_id): connected account, auto-send on/off, daily cap, how many sent today, remaining budget today, how many emails it has queued, and estimated days to drain them. It also returns mailboxes: every connected Gmail mailbox with its own account, cap and queue. Each website sends from the mailbox it is mapped to, or from the default one.

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

Input Schema

Name	Required	Description	Default
`mailbox_id`	No	A mailbox_id from the mailboxes list. Omit it for the workspace default mailbox.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / mailbox_id

Added value: +{
+  "description": "A mailbox_id from the mailboxes list. Omit it for the workspace default mailbox.",
+  "type": "string"
+}

AddedAug 14, 2026

TDQS

A3.9/5.0

Behavior4/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 real value by disclosing what data comes back (account, cap, queue depth, drain estimate) and that it always returns the full 'mailboxes' collection in addition to the selected mailbox. No rate-limit, auth, or freshness caveats are given, but the behavioral picture is solid.

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 purpose and scope are front-loaded, and the field enumeration is justified because there is no output schema. The third sentence about website-to-mailbox mapping is useful context, though the middle sentence is dense and could be trimmed slightly.

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 correctly compensates by naming the returned fields and the extra 'mailboxes' collection. The single optional parameter is fully handled, and annotations cover safety; only explicit guidance on how this relates to the other outreach_* tools is missing.

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 a single optional parameter at 100% schema description coverage, the schema already explains that mailbox_id comes from the mailboxes list and that omitting it selects the workspace default. The description echoes this rather than adding syntax, format, or edge-case detail, so the baseline 3 applies.

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?

Opens with a specific verb+resource ('Get the Gmail sending status of one mailbox') and immediately scopes it to either the workspace default or a named mailbox_id. The enumerated return fields (connected account, auto-send, daily cap, sent today, remaining budget, queue, days to drain) make the tool unmistakable next to siblings like outreach_configure_sending or outreach_list_campaigns.

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 clarifies the mailbox_id selection rule ('Omit it for the workspace default mailbox') and explains the domain model that each website sends from its mapped mailbox or the default. However, it never states when to reach for this tool versus configuring sending or inspecting campaigns, so usage is implied rather than explicit.

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

All rankparse-mcp tools Inspect

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

Need Help?