Skip to main content
Glama

SalesBlink Cold Email

Get All Senders

get_all_senders
Read-only

Get All Email Senders - Retrieve all email sender accounts (flat list, not grouped by folder)

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

Input Schema

NameRequiredDescriptionDefault
skipNo0-based page number (default: 0). The server converts this to skip × limit as the database offset.
limitNoMaximum number of senders to return (default: 100)
filterNoFilter senders by status. warmup-active: warmup on and the sender can send and receive; warmup-paused: warmup on but sending or receiving is broken
folderNoFilter by email-sender folder ID (UUID)
searchNoSearch query to filter senders
workspace_idNoWorkspace ID this action applies to. When omitted, the current or default workspace is used.

Output Schema

NameRequiredDescriptionDefault
resultNoThe raw result returned by the SalesBlink tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filter / description
      Previous value: -"Filter senders by status"New value: +"Filter senders by status. warmup-active: warmup on and the sender can send and receive; warmup-paused: warmup on but sending or receiving is broken"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are a flat list not grouped by folder, which is useful return-shape context, but it says nothing about pagination behavior, default ordering, or response limits beyond what the schema already documents.

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?

A single compact sentence with the core scope statement front-loaded and a useful clarifying parenthetical. No wasted wording.

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 read-only list tool with an output schema, six optional parameters, and full schema coverage, the description is nearly complete. A small gap remains around how the flat list interacts with the folder filter, but the structured fields already carry most of the necessary detail.

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 all six parameters are fully documented in the input schema, including the status filter enum and the skip/limit pagination semantics. The description does not add meaning beyond that schema text, making the baseline 3 appropriate.

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 states a specific verb and resource: retrieve all email sender accounts. The parenthetical '(flat list, not grouped by folder)' clarifies the shape of the result and distinguishes it from a folder-grouped view, though it doesn't name a sibling alternative directly.

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 note about being a flat list rather than grouped by folder implies a usage context, but there is no explicit guidance on when to use this versus related tools like get_sender_health or get_all_folders, nor any stated prerequisites or exclusions.

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.