Skip to main content
Glama
Sign In
Quarter4

Quarter4

by phestplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Build a content plan

content_plan
Read-only

Generate a day-by-day, per-platform content calendar for upcoming campaigns, aligning niche-aware hooks and cadence-safe posts with event phases and evergreen topics.

Instructions

Generate a day-by-day content calendar per platform for the coming weeks. Niche-aware (angles, hooks and shots fit the product), audience-aware (events ranked by relevance to the regions) and cadence-aware (email and WhatsApp capped to avoid unsubscribes). Each slot is tied to a campaign phase (tease, warm-up, early-access, launch, last-chance, thank-you) for the most important upcoming event, or an evergreen pillar on quiet days. Observances like Remembrance Day get no-sales guidance. Returns slots you then fill with captions and assets.

Input Schema

NameRequiredDescriptionDefault
brandYes
nicheYesWhat they sell, in their words, e.g. "sneakers in Lagos", "online fitness coaching"
offerNoWritten any way: "30% off", "N5k off", "BOGO", "free delivery"
formatNoDefault json
endDateNoDefault 60 days from start
productNo
regionsNoCountries, cities or codes, e.g. "Nigeria", "Lagos", "US", "UK", "worldwide"
featuredNoProducts to push, best seller first. When connected to Quarter4 Cloud this is filled from real WhatsApp order taps.
useStatsNoUse sales page stats to pick featured products (default true when connected)
platformsYesPlatforms, any spelling: instagram, tiktok, youtube, linkedin, x, facebook, pinterest, threads, whatsapp, email (also "ig", "tik tok", "newsletter", "status")
startDateNoDefault today
focusEventsNoEvents to campaign around, ids or names ("black friday", "eid", "valentines")
postsPerWeekNoPer platform; default 4
sellsProductsNofalse for creators who only publish content; default true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / featured
      Added value: +{
+  "description": "Products to push, best seller first. When connected to Quarter4 Cloud this is filled from real WhatsApp order taps.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
    • addedInput schema / properties / useStats
      Added value: +{
+  "description": "Use sales page stats to pick featured products (default true when connected)",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses substantive behavior: niche-aware angles and hooks, audience-aware event ranking by region, cadence caps for email and WhatsApp, campaign-phase slot mapping, and no-sales guidance for observances like Remembrance Day. It also clarifies that the tool returns slots rather than final captions or assets.

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?

The definition is front-loaded with the core action and then layers in scoping details compactly. The parentheticals and phase list earn their place by adding planning context without boilerplate or repetition.

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 14-parameter tool with no output schema, the description covers purpose, key behavioral constraints, and the high-level return shape. It could go further in describing the slot structure or sibling handoff, but the rich schema descriptions compensate for most gaps.

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 high at 86%, so the schema already documents most parameters. The description still adds meaning by explaining that niche affects angles, hooks and shots, regions affect event ranking, and platforms include email and WhatsApp with cadence caps, but it does not clarify every parameter such as brand, format, or useStats.

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 uses a specific verb and resource: "Generate a day-by-day content calendar per platform for the coming weeks." It also distinguishes the output from asset/caption creation by saying "Returns slots you then fill with captions and assets," which helps separate it from content_kit-style siblings.

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

Usage Guidelines3/5

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

The description implies usage for multi-platform content planning over coming weeks, including campaign-phase and observance handling. However, it does not explicitly state when to use this tool versus alternatives such as event_calendar or content_kit, nor does it give exclusions.

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

Deploy Server

Other Tools