Skip to main content
Glama

Create generated notes

create_generated_notes

Generate short notes in the writer's voice with Narrareach's note generator, from their own writing (source "profile") or from an article or post you pass in. Each note comes with a suggested time that avoids what is already on their calendar. This saves and schedules nothing: show the notes to the writer, then schedule each one they approve with schedule_note, passing the note as content, the platforms, its suggestedTime unchanged as scheduledFor (it is an absolute time) unless the writer picks another, the same workspace you used here, and this result's requestId as generationId. To schedule several approved notes at once, use schedule_notes with the same fields per note and a clientRequestId for each. Use create_draft only to keep a note unscheduled in the personal account (no workspace); it cannot save into a team workspace. Up to 10 notes per call and 20 calls per day; a call can take a minute or two.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead to spread the suggested times over. Defaults to 7.
toneNoOptional tone. Defaults to PEER_TO_PEER.
countNoHow many notes to generate. Defaults to 5. Some may be left out if they fail quality checks.
sourceNoWhat to generate from. "profile" (default) uses the writer's own writing and voice; the others need postContent and postTitle.
postUrlNoOptional link to that article or post, so notes can point to it.
timezoneNoOptional IANA time zone used when the writer has no saved posting schedule, such as America/Toronto.
platformsNoOptional platforms the notes are for, so they fit each platform's length limit.
postTitleNoThe title of that article or post. Required unless source is "profile".
workspaceNoOptional authorized team workspace name or id. Absence selects the authenticated user's personal account.
postContentNoThe article or post text to draw notes from. Required unless source is "profile".
writingLanguageNoOptional language for this batch, for example pt-BR for Portuguese. Omit or pass "auto" to use the writer's default from Settings.
cadenceResolutionNoWhat to do when the count does not fit the writer's usual posting rhythm: "extend_window" (default) spreads notes over more days; "increase_daily" posts more each day.
customInstructionsNoOptional instructions from the writer for this batch, in their words.

Output Schema

NameRequiredDescriptionDefault
toneYes
notesYes
sourceYes
cadenceNo
personaYes
qualityYes
requestIdYes
connectedAccountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / writingLanguage
      Added value: +{
      +  "description": "Optional language for this batch, for example pt-BR for Portuguese. Omit or pass \"auto\" to use the writer's default from Settings.",
      +  "enum": [
      +    "en",
      +    "pt-BR",
      +    "es",
      +    "fr",
      +    "de",
      +    "it",
      +    "auto"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior3/5

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

Adds substantial detail beyond the annotations: no persistence, suggested times avoid existing calendar entries, 10 notes per call, 20 calls per day, and one-to-two-minute latency. These are real behavioral traits the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) do not convey, so the description carries genuine value here.

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, then workflow, alternatives, and limits — no filler sentences, and the rate/latency caveat is placed where it matters. It is dense as one run-on paragraph and would read better separated, which keeps it off a 5.

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?

For a 13-parameter, non-idempotent generation tool with an output schema, the description covers what is generated, what is not persisted, downstream usage, cost limits, and latency. Return-shape explanation is correctly omitted since an output schema exists.

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 100%, so the baseline is 3; the description earns extra credit by mapping this call's outputs onto downstream parameters (note as content, suggestedTime unchanged as scheduledFor because it is absolute, workspace reused, requestId as generationId). That cross-tool semantics is not in this schema and materially reduces invocation errors.

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 ("Generate short notes") plus the two generation sources (profile vs. passed-in article/post), which uniquely identifies it against siblings like create_draft and schedule_note. An agent can tell what it produces without opening the 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?

Explicitly says what it does NOT do ("saves and schedules nothing"), then prescribes the exact next step with schedule_note / schedule_notes and their field mappings, and contrasts create_draft as the only path for unscheduled personal-account notes. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources