JustBlogged

Create post

create_post

Create a new blog post with title, HTML content, author, collection, tags, metadata, slug, image, and publishing options. status=published makes the post live. collection_id is optional; omit it to use the empty-slug default Posts collection. If that default does not exist, provide collection_id (call list_collections or create_collection).

Input Schema

Name	Required	Description	Default
`slug`	No	Post slug. Auto-generated from title when omitted.
`tags`	No	Tag names. Maximum 10 tags.
`image`	No	Optional featured image path or URL. Use upload_image for local files.
`title`	Yes	Post title.
`blogId`	Yes	Blog ID. Use list_blogs to discover available blog IDs.
`status`	No	Publishing status. Default: draft.	draft
`content`	Yes	Post HTML content.
`authorId`	No	Optional author user ID from list_blog_members. Assigning another member requires owner or admin access.
`metadata`	No	Custom metadata entries as key/value objects. Maximum 20 entries; description should be 200 characters or fewer.
`published_at`	No	Optional publish datetime in ISO 8601 format.
`collection_id`	No	Optional collection ID. When omitted, the collection with an empty slug is used. If none exists, use list_collections to choose a collection_id, or create_collection to create one first.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / collection_id / description

Previous value: -"Collection ID for the post."New value: +"Optional collection ID. When omitted, the collection with an empty slug is used. If none exists, use list_collections to choose a collection_id, or create_collection to create one first."

changedInput schema / required

Previous value: -[
-  "blogId",
-  "title",
-  "content",
-  "collection_id"
-]New value: +[
+  "blogId",
+  "title",
+  "content"
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, so the bar is lower; the description still adds real value by stating that status=published makes the post live and explaining the collection fallback chain rather than silently failing. It does not discuss permissions for authorId (delegated to schema) 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the create action and followed by the two conditionals that actually require judgment (status semantics, collection fallback). The mid-sentence field enumeration is slightly redundant but not wasteful.

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 11-param creation tool with an output schema present, the description covers the main ambiguity (which collection to target) and the mutation effect of publishing. Return values need not be explained since an output schema exists; only minor gaps like failure modes remain.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter including collection_id fallback logic and authorId access requirements. The description's field list and publishing note largely restate schema content, adding only the net effect of the status flag, so baseline 3 applies.

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?

Opens with a specific verb+resource ('Create a new blog post') and enumerates the fields it accepts, so it is immediately distinguishable from update_post, create_page, and create_blog in the sibling set.

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?

Gives concrete routing guidance: omit collection_id to use the empty-slug default Posts collection, and if that default is absent, call list_collections or create_collection. It also flags that status=published makes the post live. No explicit when-not-to-use case, which keeps it short of a 5.

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

All JustBlogged tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?