Skip to main content
Glama

Layrcake

by dev.layrcake.mcp
OverviewDiscussionsAdmin

Create draft campaign

create_campaign
DestructiveIdempotent

Create a draft email campaign with sequence steps, {{first_name}}-style variables, leads, and an optional sending window. Common sending_window.timezone values: Europe/London, Europe/Dublin, Europe/Paris, Europe/Berlin, America/New_York, America/Denver, America/Phoenix, America/Toronto, Australia/Sydney, Asia/Singapore, America/Chicago, Asia/Kolkata, Asia/Dubai. Returns removed counts for opted-out, do-not-contact, invalid, platform-blocked, or capped recipients. Active person, company and area entries are enforced even when new list creation is disabled. List management requires a signed-in person in the console or client window; there is no list-management MCP tool. Drafts never send; launch is a separate confirmed action. dry_run: true returns an advisory estimate as of evaluated_at, reserves nothing, and may differ from a later execution plan. Pass each person’s location from find_leads or enrich in leads[].location (at most 200 characters). Active area rules leave new people with no location out; removed.no_location is included in removed.do_not_contact, not added again to total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
leadsYes
stepsYes
dry_runNo
stop_on_replyNo
sending_windowNo
idempotency_keyYesA payment_required refusal means services are stopped for unpaid billing; direct the owner to the billing link in the error. Campaigns stay paused after payment until restarted. Optional for search and enrichment tools: supply one so a retry returns the original result without paying again; if that call failed with provider_unavailable, rate_limited or insufficient_credits (after a top-up), a retry runs it once more after its cooldown (30 s, or a longer retry_after_seconds; insufficient_credits as soon as the balance covers it), unless its provider may already have done the work. Required for tools that create an external side effect; reuse the same value after a timeout or an approval. A stored failure comes back with details.replayed: true; with retry_after_seconds, retry the same value after that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / leads / items / properties / location
      Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional for search and enrichment tools: supply one so a retry returns the original result without paying again; if that call failed with provider_unavailable, rate_limited or insufficient_credits (after a top-up), a retry runs it once more after its cooldown (30 s, or a longer retry_after_seconds; insufficient_credits as soon as the balance covers it), unless its provider may already have done the work. Required for tools that create an external side effect; reuse the same value after a timeout or an approval. A stored failure comes back with details.replayed: true; with retry_after_seconds, retry the same value after that."New value: +"A payment_required refusal means services are stopped for unpaid billing; direct the owner to the billing link in the error. Campaigns stay paused after payment until restarted. Optional for search and enrichment tools: supply one so a retry returns the original result without paying again; if that call failed with provider_unavailable, rate_limited or insufficient_credits (after a top-up), a retry runs it once more after its cooldown (30 s, or a longer retry_after_seconds; insufficient_credits as soon as the balance covers it), unless its provider may already have done the work. Required for tools that create an external side effect; reuse the same value after a timeout or an approval. A stored failure comes back with details.replayed: true; with retry_after_seconds, retry the same value after that."
  3. Changed1 schema field changed
    • changedInput schema / properties / sending_window / properties / timezone / enum
      Previous value: -[
-  "Etc/UTC",
-  "Etc/GMT+12",
-  "Etc/GMT+11",
-  "Etc/GMT+10",
-  "America/Anchorage",
-  "America/Dawson",
-  "America/Creston",
-  "America/Chihuahua",
-  "America/Boise",
-  "America/Belize",
-  "America/Chicago",
-  "America/Bahia_Banderas",
-  "America/Regina",
-  "America/Bogota",
-  "America/Detroit",
-  "America/Indiana/Marengo",
-  "America/Caracas",
-  "America/Asuncion",
-  "America/Glace_Bay",
-  "America/Campo_Grande",
-  "America/Anguilla",
-  "America/Santiago",
-  "America/St_Johns",
-  "America/Sao_Paulo",
-  "America/Argentina/La_Rioja",
-  "America/Araguaina",
-  "America/Godthab",
-  "America/Montevideo",
-  "America/Bahia",
-  "America/Noronha",
-  "America/Scoresbysund",
-  "Atlantic/Cape_Verde",
-  "Africa/Casablanca",
-  "America/Danmarkshavn",
-  "Europe/Isle_of_Man",
-  "Atlantic/Canary",
-  "Africa/Abidjan",
-  "Arctic/Longyearbyen",
-  "Europe/Belgrade",
-  "Africa/Ceuta",
-  "Europe/Madrid",
-  "Europe/Sarajevo",
-  "Africa/Algiers",
-  "Africa/Windhoek",
-  "Asia/Nicosia",
-  "Asia/Beirut",
-  "Africa/Cairo",
-  "Asia/Damascus",
-  "Europe/Bucharest",
-  "Africa/Blantyre",
-  "Europe/Helsinki",
-  "Europe/Istanbul",
-  "Asia/Jerusalem",
-  "Africa/Tripoli",
-  "Asia/Amman",
-  "Asia/Baghdad",
-  "Europe/Kaliningrad",
-  "Asia/Aden",
-  "Africa/Addis_Ababa",
-  "Europe/Kirov",
-  "Europe/Astrakhan",
-  "Asia/Tehran",
-  "Asia/Dubai",
-  "Asia/Baku",
-  "Indian/Mahe",
-  "Asia/Tbilisi",
-  "Asia/Yerevan",
-  "Asia/Kabul",
-  "Antarctica/Mawson",
-  "Asia/Yekaterinburg",
-  "Asia/Karachi",
-  "Asia/Kolkata",
-  "Asia/Colombo",
-  "Asia/Kathmandu",
-  "Antarctica/Vostok",
-  "Asia/Dhaka",
-  "Asia/Rangoon",
-  "Antarctica/Davis",
-  "Asia/Novokuznetsk",
-  "Asia/Hong_Kong",
-  "Asia/Krasnoyarsk",
-  "Asia/Brunei",
-  "Australia/Perth",
-  "Asia/Taipei",
-  "Asia/Choibalsan",
-  "Asia/Irkutsk",
-  "Asia/Dili",
-  "Asia/Pyongyang",
-  "Australia/Adelaide",
-  "Australia/Darwin",
-  "Australia/Brisbane",
-  "Australia/Melbourne",
-  "Antarctica/DumontDUrville",
-  "Australia/Currie",
-  "Asia/Chita",
-  "Antarctica/Macquarie",
-  "Asia/Sakhalin",
-  "Pacific/Auckland",
-  "Etc/GMT-12",
-  "Pacific/Fiji",
-  "Asia/Anadyr",
-  "Asia/Kamchatka",
-  "Etc/GMT-13",
-  "Pacific/Apia"
-]New value: +[
+  "Europe/London",
+  "Europe/Dublin",
+  "Europe/Paris",
+  "Europe/Berlin",
+  "America/New_York",
+  "America/Denver",
+  "America/Phoenix",
+  "America/Toronto",
+  "Australia/Sydney",
+  "Asia/Singapore",
+  "Etc/UTC",
+  "Etc/GMT+12",
+  "Etc/GMT+11",
+  "Etc/GMT+10",
+  "America/Anchorage",
+  "America/Dawson",
+  "America/Creston",
+  "America/Chihuahua",
+  "America/Boise",
+  "America/Belize",
+  "America/Chicago",
+  "America/Bahia_Banderas",
+  "America/Regina",
+  "America/Bogota",
+  "America/Detroit",
+  "America/Indiana/Marengo",
+  "America/Caracas",
+  "America/Asuncion",
+  "America/Glace_Bay",
+  "America/Campo_Grande",
+  "America/Anguilla",
+  "America/Santiago",
+  "America/St_Johns",
+  "America/Sao_Paulo",
+  "America/Argentina/La_Rioja",
+  "America/Araguaina",
+  "America/Godthab",
+  "America/Montevideo",
+  "America/Bahia",
+  "America/Noronha",
+  "America/Scoresbysund",
+  "Atlantic/Cape_Verde",
+  "Africa/Casablanca",
+  "America/Danmarkshavn",
+  "Europe/Isle_of_Man",
+  "Atlantic/Canary",
+  "Africa/Abidjan",
+  "Arctic/Longyearbyen",
+  "Europe/Belgrade",
+  "Africa/Ceuta",
+  "Europe/Madrid",
+  "Europe/Sarajevo",
+  "Africa/Algiers",
+  "Africa/Windhoek",
+  "Asia/Nicosia",
+  "Asia/Beirut",
+  "Africa/Cairo",
+  "Asia/Damascus",
+  "Europe/Bucharest",
+  "Africa/Blantyre",
+  "Europe/Helsinki",
+  "Europe/Istanbul",
+  "Asia/Jerusalem",
+  "Africa/Tripoli",
+  "Asia/Amman",
+  "Asia/Baghdad",
+  "Europe/Kaliningrad",
+  "Asia/Aden",
+  "Africa/Addis_Ababa",
+  "Europe/Kirov",
+  "Europe/Astrakhan",
+  "Asia/Tehran",
+  "Asia/Dubai",
+  "Asia/Baku",
+  "Indian/Mahe",
+  "Asia/Tbilisi",
+  "Asia/Yerevan",
+  "Asia/Kabul",
+  "Antarctica/Mawson",
+  "Asia/Yekaterinburg",
+  "Asia/Karachi",
+  "Asia/Kolkata",
+  "Asia/Colombo",
+  "Asia/Kathmandu",
+  "Antarctica/Vostok",
+  "Asia/Dhaka",
+  "Asia/Rangoon",
+  "Antarctica/Davis",
+  "Asia/Novokuznetsk",
+  "Asia/Hong_Kong",
+  "Asia/Krasnoyarsk",
+  "Asia/Brunei",
+  "Australia/Perth",
+  "Asia/Taipei",
+  "Asia/Choibalsan",
+  "Asia/Irkutsk",
+  "Asia/Dili",
+  "Asia/Pyongyang",
+  "Australia/Adelaide",
+  "Australia/Darwin",
+  "Australia/Brisbane",
+  "Australia/Melbourne",
+  "Antarctica/DumontDUrville",
+  "Australia/Currie",
+  "Asia/Chita",
+  "Antarctica/Macquarie",
+  "Asia/Sakhalin",
+  "Pacific/Auckland",
+  "Etc/GMT-12",
+  "Pacific/Fiji",
+  "Asia/Anadyr",
+  "Asia/Kamchatka",
+  "Etc/GMT-13",
+  "Pacific/Apia"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional for search and enrichment tools: supply one to make a retry replay the original result. Required for tools that create an external side effect; reuse the same value after a timeout or an approval."New value: +"Optional for search and enrichment tools: supply one so a retry returns the original result without paying again; if that call failed with provider_unavailable, rate_limited or insufficient_credits (after a top-up), a retry runs it once more after its cooldown (30 s, or a longer retry_after_seconds; insufficient_credits as soon as the balance covers it), unless its provider may already have done the work. Required for tools that create an external side effect; reuse the same value after a timeout or an approval. A stored failure comes back with details.replayed: true; with retry_after_seconds, retry the same value after that."
  5. Changed1 schema field changed
    • addedInput schema / properties / steps / items / properties / wait_days / description
      Added value: +"Days to wait after the previous step before this step is sent. Ignored on the first step, which sends at launch within the sending window."
  6. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Stable retry key; the same value identifies retries of the same request after timeout or approval."New value: +"Optional for search and enrichment tools: supply one to make a retry replay the original result. Required for tools that create an external side effect; reuse the same value after a timeout or an approval."
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover safety flags, but the description adds genuinely non-derivable behavior: what `removed` counts mean (opted-out, do-not-contact, invalid, platform-blocked, capped), that active person/company/area entries are enforced even when new list creation is disabled, that drafts never send, and that dry_run reserves nothing and may differ from a later plan. This is rich disclosure beyond the structured fields.

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?

Front-loaded with purpose and the create-vs-launch distinction, and every sentence carries operational content. It is dense and interleaves several concerns (billing, list management, area-rule edge cases), with some granularity that borders on padding ('removed.no_location is included in removed.do_not_contact'), but nothing is clearly wasted.

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 7-param, nested, non-read-only tool with no output schema and low schema coverage, the description supplies the return-side essentials (`removed` accounting), the dry-run contract, and enforcement rules. The main gap is that it doesn't document most nested lead/step fields, which the schema carries only via types and constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 14%, so the description has to compensate — and it does for the highest-risk params: sending_window.timezone (names common values), dry_run (advisory/reserves-nothing semantics), and leads[].location (source from find_leads/enrich, 200-char cap). It does not add meaning for name, the other lead fields, or step body/subject/wait_days, so it falls short of full compensation.

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 first sentence gives a specific verb+resource (create a draft email campaign) plus the shape of the payload (sequence steps, variables, leads, optional sending window). It also explicitly distinguishes itself from the sibling launch_campaign: 'Drafts never send; launch is a separate confirmed action.' An agent can route between create and launch 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?

Gives clear context for use and non-use: drafts never send, launch is a separate confirmed action, and there is no list-management MCP tool (so list management must happen elsewhere). It also explains when to reach for dry_run. It stops short of a full when-to-use/when-not matrix against all siblings, but the boundaries are clear.

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

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