Skip to main content
Glama

Notipo

by io.github.kfuras

Create Post

create_post

Create a new blog post. Creates a Notion page and triggers sync to WordPress. The body should be markdown. Set publish=true to publish immediately, or leave false to create a draft.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoPost content in markdown
slugNoCustom URL slug
tagsNoTag names
titleYesPost title
publishNoPublish immediately (true) or create as draft (false)
categoryNoCategory name
seoKeywordNoSEO focus keyword
seoDescriptionNoCustom meta description for SEO (max 160 chars). Auto-derived from content if not set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesUse get_job to poll status
notionPageIdYes

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses that the tool 'Creates a Notion page and triggers sync to WordPress,' which is a significant side effect beyond what the annotations (`readOnlyHint: false`) convey. This adds valuable context about the multi-system impact of the operation, going beyond the minimum that annotations alone would suggest.

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 exceptionally tight—four short sentences that front-load the core action and pack in side effects (Notion + WordPress), format (markdown), and publish semantics (draft vs. immediate). Every sentence earns its place with zero fluff.

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 tool with a well-populated schema and annotations, the description covers all non-obvious aspects: the Notion/WordPress workflow, markdown requirement, and publish toggle behavior. It doesn't discuss tags, slug, or category, but these are self-explanatory and fully described in the schema, making the description sufficiently complete.

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?

With 100% schema coverage, the schema already documents all 8 parameters clearly. The description adds marginal value by specifying 'The body should be markdown'—a format hint not present in the schema—and rephrasing the `publish` behavior. This pushes it slightly above the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Create a new blog post') and immediately adds distinguishing context about creating a Notion page and syncing to WordPress. While the core purpose is crystal clear, it doesn't explicitly differentiate from sibling tools like `direct_publish` or `publish_post`, so it earns a 4 rather than a 5.

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

Usage Guidelines3/5

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

The description implies usage context—creating blog posts with markdown content—and explains the two modes via the `publish` flag ('Set publish=true to publish immediately, or leave false to create a draft'). However, it never explicitly addresses when to use this tool versus the sibling `direct_publish` for immediate publishing, which feels like a missed opportunity given the overlapping functionality.

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

All Notipo toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Most tools target clearly distinct resources and actions, separating creation, updates, deletions, list/get operations, and job monitoring. The main ambiguity is between direct_publish and publish_post, since both involve publishing, though their descriptions clarify creation vs. making a draft live.

Naming Consistency4/5

The majority of tools follow a clear verb_noun pattern: create_post, get_post, list_posts, update_post, delete_post, publish_post, list_categories, list_tags. The exceptions are direct_publish and sync_now, which deviate from the pattern but remain understandable.

Tool Count5/5

13 tools is well-scoped for a blogging and sync workflow covering posts, publishing, jobs, categories, tags, and settings. Each tool addresses a distinct part of the pipeline without redundancy or excessive granularity.

Completeness4/5

The surface covers the core post lifecycle, publishing jobs, sync triggers, WordPress metadata, and settings. The only notable gap is that direct_publish creates a WordPress post outside of Notion, while update_post explicitly syncs back from Notion, so updating a direct-published post may not be covered.

Resources