Skip to main content
Glama

Update the writing voice

flypost_update_writing_voice
Destructive

Change the project's writing voice (Project Settings > Voice): the voice guide, words to avoid, and formatting rules. Every post, article and slide the app writes follows these, and so must you. Each field you pass REPLACES that field, so read flypost_get_writing_voice first and send the full new text (e.g. add a word to the existing avoid list, do not send just the new word). Pass null to clear a field. Change them when the user asks you to remember a style rule.

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_update_writing_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project set with flypost_use_project.
avoid_wordsNo
voice_guideNo
content_focusNoWhat posts should be about, e.g. top-of-funnel only. Steers ideas as well as posts.
formatting_rulesNo
use_best_practicesNoWhether Flypost's writing best practices (opening and closing advice, post styles) shape posts. False means only the voice guide does, and needs a voice guide to take effect. Facts and format rules always apply.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The annotations mark this as destructive and not read-only, and the description adds the critical behavioral detail that each passed field REPLACES the existing field. It further warns to read first and send full new text, and explains that null clears a field, which is exactly the risk context needed for a destructive update.

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 description is front-loaded with the resource and action, then immediately covers the replacement risk, the read-first prerequisite, null clearing, and usage context. Every sentence contributes either scope, safety, or invocation guidance.

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 destructive mutation tool with no output schema, the definition covers the essential risks: replacement of existing fields, the need to read before writing, full-text submission, null clearing, and when to use it. The remaining parameters are documented in the input schema, so the description is complete enough for correct invocation.

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 only 50%, so the description must add meaning. It does so for the voice guide, avoid words, and formatting rules by explaining replacement semantics, full-text requirements, and null clearing. It does not describe every parameter, but the schema already documents project_id, content_focus, and use_best_practices.

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 states a specific verb and resource: changing the project's writing voice, specifically the voice guide, avoid words, and formatting rules. It explicitly names flypost_get_writing_voice as the read counterpart, so the agent can distinguish this mutating tool from the getter 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 Guidelines5/5

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

It gives clear when-to-use guidance: change these when the user asks to remember a style rule. It also names the required prerequisite, flypost_get_writing_voice, and explains that fields must be sent as full replacement text rather than deltas.

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.