Notipo

Direct Publish

direct_publish

Publish a blog post directly to WordPress without Notion. Handles image uploads, Gutenberg conversion, featured image generation, and SEO metadata. Body must be markdown. Set publish=true to go live, false for draft. Use this instead of create_post when you don't need Notion.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Post content in markdown (required)
`slug`	No	Custom URL slug
`tags`	No	Tag names
`title`	Yes	Post title
`publish`	No	Publish immediately (true) or create as draft (false)
`category`	No	Category name
`imageTitle`	No	Featured image title/text overlay
`seoKeyword`	No	SEO focus keyword
`seoDescription`	No	Custom meta description for SEO (max 160 chars)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`jobId`	Yes	Use get_job to poll status

TDQS

A4.6/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, so the description adds value by detailing side effects: image uploads, Gutenberg conversion, featured image generation, and SEO metadata handling. It also clarifies draft vs. live behavior. Slightly more could be said about reversibility or permission requirements, but the core behavior is disclosed.

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?

Two sentences, front-loaded with purpose, and every phrase adds value. No fluff or repetition of obvious schema details.

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 a tool with 9 parameters and an output schema, the description captures the core workflow, key constraints, and positioning relative to siblings. It does not list every parameter but the schema already covers that; the description is complete enough for an agent to decide and invoke correctly.

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 100%, so baseline is 3. The description adds extra meaning beyond the schema: 'Body must be markdown' imposes a format constraint not in the schema, and it clarifies the integration between publish flag and go-live vs. draft. This compensates 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 opens with a specific verb and resource: 'Publish a blog post directly to WordPress without Notion.' It clearly distinguishes from sibling tools by naming create_post as an alternative when Notion is needed.

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?

Explicitly states when to use this tool: 'Use this instead of create_post when you don't need Notion.' Also provides essential usage constraints like 'Body must be markdown' and the publish flag behavior.

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

All Notipo tools Inspect

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.

Direct Publish

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources