Skip to main content
Glama
Sign In

Sending

by dev.sending
OverviewDiscussionsAdmin

Start ActiveCampaign import

start_activecampaign_import
Destructive

Starts an import from ActiveCampaign (uses the credentials already connected with connect_activecampaign). entities/options are optional; default: import everything, non-destructive merge. Campaigns come in as historical content (never rescheduled) and automations as DRAFTS to review (never active): use get_import_status to read, automation by automation, what was not converted. Requires the contacts:write scope.

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

Input Schema

NameRequiredDescriptionDefault
optionsNooverwriteExisting: overwrites existing attributes (default false). convertAutomationsWithAi: translates automation blocks with AI (default true, consumes AI credits).
entitiesNoEntities to import (default: all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entities / description
      Previous value: -"Entita da importare (default: tutte)."New value: +"Entities to import (default: all)."
    • changedInput schema / properties / options / description
      Previous value: -"overwriteExisting: sovrascrive gli attributi esistenti (default false). convertAutomationsWithAi: traduce i blocchi delle automazioni con l'AI (default true, consuma crediti AI)."New value: +"overwriteExisting: overwrites existing attributes (default false). convertAutomationsWithAi: translates automation blocks with AI (default true, consumes AI credits)."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With destructiveHint=true and openWorldHint=true already declared, the description adds real value: the default is a non-destructive merge, campaigns land as historical content that is never rescheduled, and automations arrive as inactive DRAFTS. It also discloses the required contacts:write scope. It stops short of covering rate limits or the shape of the start response, so a 4 rather than 5.

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?

It is a dense single paragraph with no filler and leads with the action and prerequisite. The clauses are all load-bearing, though the length is at the upper edge of what is comfortable for a tool with only two optional parameters.

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?

No output schema exists, but the description compensates by directing the agent to get_import_status and describing the two non-obvious behaviors (campaigns never rescheduled, automations as drafts). With annotations and a fully documented schema, nothing material is missing for correct invocation.

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% and both nested objects are documented (including defaults for overwriteExisting and convertAutomationsWithAi), so the schema carries the parameter burden. The description restates only that entities/options are optional with 'import everything' as the default, adding little beyond the schema. 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?

The description states a specific verb and resource ('Starts an import from ActiveCampaign') and immediately scopes it against related tools by naming the prerequisite (connect_activecampaign) and the read-back sibling (get_import_status). An agent can distinguish this from the many create_* siblings without opening a schema.

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

Usage Guidelines5/5

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

It gives the enabling precondition ('uses the credentials already connected with connect_activecampaign'), spells out the default operating mode, and routes the agent to get_import_status for inspecting results. This is explicit when-to-use plus named alternatives rather than inference.

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

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