Skip to main content
Glama
lindoai

mcp-lindoai

Official

publish_blog

Publish a static blog post using markdown content. Provide URL path, title, and optional metadata to create blog entries on your website.

Instructions

Publish a static blog post with markdown content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
pathYesURL path (e.g. /blog/my-post)
blog_contentYesMarkdown content
page_titleYesBlog title
authorNoAuthor name
excerptNoBrief summary
categoryNoCategory
publish_dateNoDisplay date

Implementation Reference

  • Registration of the 'publish_blog' tool using server.tool(), which defines the schema, metadata, and handler.
    server.tool(
      "publish_blog",
      "Publish a static blog post with markdown content.",
      {
        website_id: z.string().describe("The website ID"),
        path: z.string().describe("URL path (e.g. /blog/my-post)"),
        blog_content: z.string().describe("Markdown content"),
        page_title: z.string().describe("Blog title"),
        author: z.string().optional().describe("Author name"),
        excerpt: z.string().optional().describe("Brief summary"),
        category: z.string().optional().describe("Category"),
        publish_date: z.string().optional().describe("Display date"),
      },
      { title: "Publish Blog Post", readOnlyHint: false, destructiveHint: false, openWorldHint: true },
      async ({ website_id, path, blog_content, page_title, author, excerpt, category, publish_date }) => {
        const body = {
          path,
          blog_content,
          seo: { page_title },
          blog_settings: {
            ...(author && { author }),
            ...(excerpt && { excerpt }),
            ...(category && { category }),
            ...(publish_date && { publish_date }),
          },
        };
        const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/create`, "POST", body);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input validation schema using Zod for publish_blog, defining all parameters: website_id, path, blog_content, page_title, author, excerpt, category, publish_date.
    {
      website_id: z.string().describe("The website ID"),
      path: z.string().describe("URL path (e.g. /blog/my-post)"),
      blog_content: z.string().describe("Markdown content"),
      page_title: z.string().describe("Blog title"),
      author: z.string().optional().describe("Author name"),
      excerpt: z.string().optional().describe("Brief summary"),
      category: z.string().optional().describe("Category"),
      publish_date: z.string().optional().describe("Display date"),
    },
  • Handler function for publish_blog that builds the request body and calls the API endpoint POST /v1/workspace/website/{website_id}/blogs/create.
    async ({ website_id, path, blog_content, page_title, author, excerpt, category, publish_date }) => {
      const body = {
        path,
        blog_content,
        seo: { page_title },
        blog_settings: {
          ...(author && { author }),
          ...(excerpt && { excerpt }),
          ...(category && { category }),
          ...(publish_date && { publish_date }),
        },
      };
      const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/create`, "POST", body);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Generic apiCall helper used by the handler to perform authenticated HTTP requests to the Lindo AI API.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior2/5

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

The description lacks behavioral details beyond the action 'publish,' such as whether it overwrites existing content, requires a blog to exist, or affects SEO. Annotations indicate non-destructive and open world, but no additional context is given. No contradiction with annotations.

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, highly concise, no redundancy. Front-loaded with key action and resource.

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?

Despite clear purpose, the description omits important context: prerequisites (e.g., blog must exist via create_blog?), behavior on re-publishing, and return values. With 8 parameters and no output schema, more guidance is needed.

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% (8/8 parameters documented), so the baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides.

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 the action 'publish' and the resource 'static blog post' with format 'markdown content'. It effectively distinguishes from sibling tools like create_blog or update_blog by focusing on making the post live.

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?

No explicit guidance on when to use this tool versus alternatives like create_blog or unpublish_blog. The context is implied but not stated, and no when-not-to-use conditions are provided.

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/lindoai/mcp-server'

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