Skip to main content
Glama
kravionatech

kraviona-admin

by kravionatech

create_post

Create a blog post with SEO metadata, category, featured image, and content. Supports draft or published status.

Instructions

Create a new blog post with full SEO metadata, category, featured image, and content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoURL slug (auto-generated from title if omitted)
titleYesPost title
statusNoPost status (default: draft)
contentYesHTML content of the post
excerptNoShort description / meta description
ogTitleNoOpen Graph title for social sharing
categoryNoCategory slug e.g. technical-seo, ai-and-automation
metaTitleNoSEO meta title (60 chars max)
canonicalUrlNoCanonical URL if different from default
metaKeywordsNoSEO keywords array
ogDescriptionNoOpen Graph description for social sharing
metaDescriptionNoSEO meta description (160 chars max)
featuredImageAltNoFeatured image alt text
featuredImageUrlNoFeatured image URL (from Unsplash or Cloudinary)
contentSourceTypeNoContent source type (default: Human)
primaryTopicClusterNoPrimary topic cluster / pillar keyword for the post
Behavior2/5

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

No annotations are provided, so the description carries full burden. It lacks disclosure on behavioral traits like whether the post is published immediately, what happens on duplicate slug, or any side effects.

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?

Single sentence front-loaded with verb and resource. No wasted words; every part earns its place.

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

Completeness2/5

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

For a tool with 16 parameters and no output schema or annotations, the description is incomplete. It does not mention return value, required permissions, or any side effects.

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 coverage is 100%, so baseline is 3. The description adds a high-level summary ('full SEO metadata') but no additional semantic meaning beyond what the property descriptions already provide.

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 uses a specific verb ('Create') and resource ('blog post'), lists key features (SEO metadata, category, featured image, content), and clearly distinguishes from siblings like update_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 (e.g., when to create vs. update/publish). No mention of prerequisites or context for use.

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/kravionatech/mcp-kraviona'

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