Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Draft a newsletter post

connections_newsletter_create_post

Start a new draft post on a newsletter, optionally with a title, subtitle, preview text and an HTML body. Nothing is published or sent - it waits as a draft for the member. Call this when the member asks to draft their next issue.

Input Schema

NameRequiredDescriptionDefault
titleNoThe post's title.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
dry_runNoPreview only.
projectNoWorkspace to run this call in (id or name).
bodyHtmlNoThe post body as simple HTML (paragraphs, headings, lists, links). {{name}} and {{email}} are filled per subscriber.
subtitleNoThe line shown under the title.
previewTextNoThe grey snippet line an inbox shows beside the subject.
publicationIdYesId from list_publications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only; nothing is written."New value: +"Preview only."
    • changedInput schema / properties / publicationId / description
      Previous value: -"The publication's id, from list_publications."New value: +"Id from list_publications."
  2. Changed2 schema fields changed
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: return what this call would do, with nothing written."New value: +"Preview only; nothing is written."
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds real value by stating the result is a draft that waits for the member and is never published or sent, which tells the agent the write is safe and reversible. It does not say what happens to the response (returned draft id) or what dry_run previews, so a small gap remains.

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?

Two sentences, front-loaded with what is created and followed by the key safety fact and the trigger condition. No filler, no repetition of the title.

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 an 8-parameter creation tool with full schema coverage and clear annotations, the description covers the essential what, when, and non-destructive outcome. The main omission is any hint of what the call returns (e.g. a post id needed to subsequently edit or fetch the draft), which an agent would only learn after invoking it.

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 100%, so the schema already explains every parameter, including publicationId, person, project and dry_run. The description only restates the four content fields and marks them optional, which slightly reinforces the schema's required/optional split but adds no new meaning. Baseline 3 is correct.

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 gives a specific verb and resource ("Start a new draft post on a newsletter") and enumerates the optional fields it accepts, so the agent knows exactly what is created. It does not explicitly contrast itself with siblings such as connections_newsletter_get_post or connections_newsletter_list_posts, which keeps it just short of a 5.

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?

"Call this when the member asks to draft their next issue" is an explicit triggering condition, and "Nothing is published or sent" clarifies when it is not a send operation. However, it names no alternative for related tasks (editing an existing draft, publishing, listing publications), so the agent must infer the boundary itself.

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

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