Skip to main content
Glama

Write a Pulse article (server pipeline)

flypost_generate_article
Destructive

Final step of Flypost's own long-form writer: write the full article from its brief, blocking up to ~20 minutes. Prefer flypost_save_article when you can write the article yourself — it is faster and costs the user nothing. Normally run flypost_prepare_article and flypost_outline_article first; with only a topic it creates the article and writes it straight away. Pass feedback to refine an existing body, which it replaces. Always set target_query: it steers the writer and is what keyword tracking reports on. The article keeps the type set at prepare (article_type); pass it here only when creating straight from a topic.

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

Input Schema

NameRequiredDescriptionDefault
angleNo
topicNoTopic for a new article when article_id is omitted.
feedbackNoImprovement feedback on the current body.
article_idNo
project_idNoProject id; omit for the active project.
notebook_idNoWrite from ONE notebook: the brief, outline and article retrieve only from its sources. Pass the source_package_id that flypost_create_notebook returns (or a notebook id from flypost_list_sources). Typical flow when you did the research yourself: flypost_create_notebook, then save each finding with flypost_add_source_url or flypost_add_source_text (one source per tool or page you researched), then flypost_prepare_article with notebook_id and research_mode "source". For a roundup, everything comes from the notebook: save a source per tool (your own company and, for "X alternatives", X itself included), with the tool named in its title or saved from its own site so it can be matched. With research_mode "source" a tool the notebook does not cover is left out. Set on a new article, or moves an existing one onto that notebook.
article_typeNoThe article format. guide (default): explains how or why in 4-7 sections ("how to measure share of voice"). list: numbered points, one per H2, count taken from the brief ("10 questions to ask an agency", "a 25-point checklist"). roundup: "best X for Y" written by the author in the first person as having tested the tools ("I tested 8 Taplio alternatives: here are the best"), one H2 per entry with the same sub-structure, a how-I-chose section, a comparison and an FAQ; every entry is researched first (from the notebook when notebook_id is set, else one web search per entry) and only sourced facts are used, so it takes longer. Match it to target_query. Omitted on a new article = guide.
target_queryNoThe exact search query the article is trying to rank for, e.g. "what is an impression on linkedin". Steers the writer's retrieval and prompts, and is the keyword the app's rankings report tracks. Sets it on a new article, or updates it on an existing one.
research_modeNosource: ground only on the Brain (or on notebook_id when given). online: also research the web. With notebook_id, source keeps the article to that notebook with no web search at all; online adds fresh web stats and, for a roundup, web research for whatever the notebook does not cover (entries, the tool being replaced). A roundup with no notebook should use online: its entries need live pricing and features.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructive and open-world annotations, it discloses blocking duration of up to ~20 minutes, that feedback replaces the existing body, and that roundups take longer due to research. It also explains notebook grounding and when web research is added, which is substantial context for a long-running mutation.

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?

The description is front-loaded with the core action, the blocking warning, and the preferred alternative, then moves into prerequisites and parameter guidance. It is dense but mostly earns its length, though a few notebook-related details could be tightened.

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 complex nine-parameter, long-running writer with no output schema, the description covers the pipeline context, alternatives, cost, duration, mutation behavior, grounding modes, and key parameter requirements. An agent has enough information to invoke it correctly and avoid unnecessary calls.

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 description coverage is high, so the baseline is 3, but the description adds operational meaning: target_query must always be set because it steers the writer and keyword tracking, article_type is normally inherited from prepare, and notebook_id changes grounding behavior. It could have said more about angle, but the key parameters are clarified.

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?

It states a specific verb and resource: writes the full article from a brief as the final step of Flypost's long-form pipeline. It distinguishes itself from sibling flypost_save_article and from the earlier prepare/outline steps, so an agent can identify its role 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?

It gives explicit when-to-use and when-to-prefer-alternative guidance: prefer flypost_save_article when writing manually, normally run prepare and outline first, or pass only a topic to write immediately. It also covers feedback-based refinement and the required target_query, leaving little to inference.

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.