Skip to main content
Glama
laxmena

writefreely-mcp-server

publish_post

Publish a Markdown post to WriteFreely, anonymously or to a specific collection with an optional title.

Instructions

    Create and publish a new post on WriteFreely.
    Supports anonymous posts or publishing to a specific collection/blog.

    Args:
        content:     The main body of the post (Markdown supported)
        title:       Optional post title
        access_token: Access token from login() or WRITEFREELY_ACCESS_TOKEN env var
                     Leave empty for anonymous publishing or to use env var token
        collection:  Optional blog/collection alias to publish into
                     (only works with access_token)

    Returns:
        Success message with post URL or error
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
titleNo
access_tokenNo
collectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description covers key behaviors: supports anonymous posts, Markdown, collection parameter requires access_token, and returns post URL or error. Could add details about idempodency or rate limits.

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 concise, well-structured with Args list and Returns, every sentence adds value, no redundancy.

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?

The description covers main usage, parameters, return value. Output schema exists, so return details are sufficient. Missing details like synchronous behavior or error handling specifics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description thoroughly explains each parameter: content supports Markdown, title optional, access_token from login() or env var, collection only with token. This adds significant meaning beyond 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?

The description clearly states the tool creates and publishes a new post on WriteFreely, distinguishing anonymous posts from collection publishing. It is distinct from sibling tools like edit_post or read_post.

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?

The description indicates when to use the tool (to create/publish). It explains anonymous vs authenticated usage but does not explicitly contrast with siblings or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laxmena/writefreely-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server