Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

List Instantly sending accounts

list_instantly_accounts
Read-only

Fetches the sending accounts of an Instantly.ai workspace using your Instantly API key, together with a pre-filled CSV for Emailchaser's bulk IMAP/SMTP connection flow. A read-only preview before an import: nothing is written to the workspace. Mailbox passwords cannot be exported from any provider, so each account is either reconnected via Google/Microsoft OAuth in the app or bulk-uploaded with app passwords using the CSV. The backend treats all non-GET calls as writes, so this needs a read & write API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instantlyApiKey": "<instantlyApiKey>"
    },
    "name": "list_instantly_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
instantlyApiKeyYesYour Instantly.ai API key (Instantly → Settings → API keys)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'nothing is written to the workspace'. It adds genuinely non-obvious context absent from the annotations: the API key needs read & write scope because the backend treats non-GET calls as writes, and mailbox passwords cannot be exported at all. The one gap is that the returned CSV format/shape is not characterized, but the safety and auth profile are well covered.

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 most important fact, that this is a read-only preview fetch plus a CSV, is front-loaded in the first sentence. Four sentences are a bit dense, and the OAuth/app-password explanation, while useful for choosing a follow-up path, is slightly beyond the tool's own contract.

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 carries the burden of explaining what comes back, and it does identify both return artifacts (accounts and a pre-filled CSV). It also covers the auth scope requirement, which is essential since the key alone could fail. Only the exact structure of the CSV and any pagination/limit behavior are left unstated.

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?

There is a single parameter at 100% schema description coverage, and the schema already tells the agent where to find the key. The description only reinforces that the key is a workspace API key and hints at its required scope, adding little meaning beyond the schema. Baseline 3 is appropriate.

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 names a specific verb and resource ('Fetches the sending accounts of an Instantly.ai workspace') and goes further by stating what else is returned (a pre-filled CSV for Emailchaser's bulk IMAP/SMTP flow). It distinguishes itself from the write-side sibling by framing the call as 'a read-only preview before an import', so an agent can separate it from import_instantly without opening either schema.

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?

Usage context is clear and specific: use this as a preview step before importing accounts into Emailchaser, then either reconnect via OAuth or bulk-upload via the returned CSV. It does not explicitly name the alternative tool to call next or state a when-not-to-use condition, which keeps it just short of a 5.

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

All Emailchaser 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