Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

List newsletter posts

connections_newsletter_list_posts
Read-only

List a newsletter's posts, most recently edited first, without their bodies: title, subtitle, whether each is a draft or published on the web, and whether and when it was emailed and to how many. Call this when someone asks about their issues, drafts, or what they sent last.

Input Schema

NameRequiredDescriptionDefault
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
statusNoOnly drafts, or only published posts.
projectNoWorkspace to run this call in (id or name).
publicationIdYesId from list_publications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / publicationId / description
      Previous value: -"The publication's id, from list_publications."New value: +"Id from list_publications."
  2. Changed1 schema field changed
    • 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.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral detail beyond them: result ordering, exclusion of post bodies, and the exact fields returned including email status and recipient counts. It stops short of stating pagination or result limits, which matters for a listing endpoint.

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, no filler, with the distinguishing constraint (no bodies) and the ordering front-loaded before the usage cue. Every clause carries information an agent needs.

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 usefully enumerates the returned fields (title, subtitle, draft/published state, email timing and audience size), which is exactly what the missing output schema would have provided. The remaining gap is pagination/limit behavior, a notable omission for a list tool but not fatal.

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%, so the schema already explains person, status, project, and publicationId. The description only implies publicationId via "a newsletter's posts" and says nothing extra about the draft/published status filter or the act-as/workspace parameters, so it does not exceed the baseline.

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?

States a specific verb and resource ("List a newsletter's posts") plus ordering ("most recently edited first") and an explicit scope boundary ("without their bodies"). The body-omission clause implicitly separates it from connections_newsletter_get_post, so an agent can pick the right tool 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?

"Call this when someone asks about their issues, drafts, or what they sent last" gives concrete triggering intents, which is strong positive guidance. It does not name an alternative for the case where full post content is needed (get_post), so the when-not side is left implicit.

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