Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Preview an outreach campaign

outreach_preview
Read-onlyIdempotent

The emails of one step as they will go, for real people of the campaign: who it goes to, from which mailbox, the subject and the text with every placeholder filled and the unsubscribe line Conecto adds (each person gets their own link, so the preview shows where it goes). Show the person the first emails before you start a campaign. Also the writing check's fixes, if any. Free.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "outreach_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNo
emailNoOne person of the campaign.
limitNo
campaign_idYesThe campaign_id outreach_save_campaign answered with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description appropriately adds preview-specific context: placeholders are filled, each recipient gets a unique unsubscribe link, writing-check fixes are included, and the operation is free. It does not add rate-limit or response-shape details, keeping it just short of full transparency.

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 front-loaded with what the preview contains and uses only three sentences. The first sentence is long and packed with parenthetical detail, but every part adds useful preview semantics rather than repeating annotations or schema.

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 and only partial parameter descriptions, the description does most of the work by explaining what the preview shows: recipient, mailbox, subject, filled text, unsubscribe link, and writing-check fixes. It is complete enough for an agent to understand the call, though limit behavior and detailed return structure remain unspecified.

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 coverage is 50%, with campaign_id and email described in the schema while step and limit lack descriptions. The description conceptually implies step selection and a limited set of first emails, but it does not explicitly map these to the step and limit parameters or clarify their behavior.

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 states exactly what is returned: the rendered emails of one campaign step, including recipient, mailbox, subject, filled placeholders, unsubscribe line, and writing-check fixes. It also distinguishes the operation from starting a campaign by framing it as a pre-start preview.

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?

It gives explicit timing guidance: show the first emails before starting a campaign. This clearly routes the agent away from outreach_start for inspection purposes, though it does not name the sibling tool or discuss when not to preview.

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

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