Skip to main content
Glama

Brainstorm ideas (server pipeline)

flypost_brainstorm_ideas

Run Flypost's tuned brainstorm pipeline: generates post ideas from the Brain or a specific notebook. Blocks until the ideas land (typically 1-3 minutes). The ideas then develop in the background from the Brain, as they do when kept in the app, so they're ready to open; an idea the Brain can't support comes back marked as needing web research instead. For agent-authored ideas use flypost_save_idea instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_format": "<target_format>"
    },
    "name": "flypost_brainstorm_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional seed topic to steer ideation.
project_idNoProject id; omit for the active project.
recent_daysNoIdeate only from material added to the Brain in the last N days (no topic, whole Brain). Too little recent material falls back to the whole Brain.
auto_developNoDevelop each idea in the background from the Brain once it lands (default true). Set false when you will develop only the ideas you pick.
concept_countNo
research_modeNo
target_formatYesThe post format the idea targets.
source_package_idNoIdeate from one notebook; omit to ideate across the whole Brain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare mutation, no-destroy, and open-world; the description adds genuinely useful behavior: it blocks (1-3 minutes typical), development continues in the background, and unsupported ideas return marked as needing web research. It does not disclose cost, credit usage, or what happens if the call times out mid-wait, which keeps it from a 5.

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?

Three sentences, front-loaded with the core action and latency, followed by downstream behavior and the sibling redirect. No filler or repeated schema content.

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, non-destructive but mutating, long-running tool with no output schema, the definition covers timing, background continuation, and failure-mode signaling. It stops short of describing the shape of the returned ideas or defaults for concept_count and target_format, which would help an agent act on the result.

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 75%, so the baseline is 3, but the description adds meaning beyond the schema: the background-development sentence explains the default of auto_develop, and the "needing web research" outcome clarifies the practical effect of research_mode. It never names concept_count, recent_days, or target_format directly, leaving those to the schema.

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 ("generates post ideas from the Brain or a specific notebook") and names the sibling tool to use for the other case ("For agent-authored ideas use flypost_save_idea instead"). An agent can distinguish this from flypost_save_idea 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?

Explicitly routes agent-authored ideas to flypost_save_idea and explains the default auto-develop path versus keeping ideas undeveloped. It does not address when to prefer other server-side ideation entries such as flypost_build_first_ideas, so it stops short of full alternative coverage.

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.