Skip to main content
Glama
laxmena

writefreely-mcp-server

delete_post

Permanently remove a post from WriteFreely using its post ID. Requires authentication or edit token for anonymous posts.

Instructions

    Permanently delete a post.

    Args:
        post_id: The ID of the post to delete
        access_token: Access token from login() or WRITEFREELY_ACCESS_TOKEN env var
                     (optional if token is set via env var)
        edit_token: Edit token for anonymous posts (from publish_post response)

    Returns:
        Success or error message
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYes
access_tokenNo
edit_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so the description carries full burden. It mentions 'permanently delete' and parameter details, but lacks disclosure of irreversible effects, required permissions, or error conditions.

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 with clear Args and Returns sections, using minimal sentences without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete tool with no output schema, the description covers basic usage. However, it lacks context on error handling, deletion limitations (e.g., can't delete others' posts), and differentiation from edit_post.

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 has 0% description coverage, and the description adds significant meaning for all three parameters: post_id, access_token (with optional env var fallback), and edit_token (source for anonymous posts).

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 'Permanently delete a post', specifying the action and resource. It distinguishes from sibling tools like edit_post or publish_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like edit_post, or prerequisites such as ownership or authentication requirements beyond parameter hints.

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