Skip to main content
Glama
lindoai

mcp-lindoai

Official

Publish Page

publish_page

Publish a static HTML page to your Lindo AI website by specifying the URL path, page title, and HTML content.

Instructions

Publish a static page with HTML content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
pathYesURL path (e.g. /about)
page_contentYesPage content in HTML
page_titleYesPage title for SEO

Implementation Reference

  • The handler function that executes the publish_page tool logic. It takes website_id, path, page_content, and page_title as input, constructs a body object with SEO info, makes a POST request to /v1/workspace/website/{website_id}/pages/create, and returns the result.
    async ({ website_id, path, page_content, page_title }) => {
      const body = {
        path,
        page_content,
        seo: { page_title },
      };
      const data = await apiCall(`/v1/workspace/website/${website_id}/pages/create`, "POST", body);
      return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
    }
  • The input schema for the publish_page tool, defining required parameters: website_id, path, page_content, and page_title, all validated as strings via Zod.
      inputSchema: {
      website_id: z.string().describe("The website ID"),
      path: z.string().describe("URL path (e.g. /about)"),
      page_content: z.string().describe("Page content in HTML"),
      page_title: z.string().describe("Page title for SEO"),
    },
  • The full registration of the publish_page tool using server.registerTool() with its name, metadata (title, description, annotations), input schema, and handler function.
    server.registerTool(
      "publish_page",
      {
        title: "Publish Page",
        description: "Publish a static page with HTML content.",
        inputSchema: {
        website_id: z.string().describe("The website ID"),
        path: z.string().describe("URL path (e.g. /about)"),
        page_content: z.string().describe("Page content in HTML"),
        page_title: z.string().describe("Page title for SEO"),
      },
        annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: true },
      },
      async ({ website_id, path, page_content, page_title }) => {
        const body = {
          path,
          page_content,
          seo: { page_title },
        };
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/create`, "POST", body);
        return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
      }
    );
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-destructive. The description adds minimal behavioral detail beyond the word 'publish', which implies making content live. No mention of side effects or access requirements.

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?

Single sentence, efficient and to the point. However, it could be slightly more informative without becoming verbose.

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

Completeness3/5

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

Given no output schema and simple parameters, the description is adequate for basic understanding. However, it fails to clarify workflow context (e.g., whether the page must first be created via `create_page`), which is important given sibling tools.

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?

Input schema has 100% description coverage for all parameters. The description does not add any additional 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), resource (page), and content type (HTML). It distinguishes from sibling tools like `create_page` (creation) and `unpublish_page` (opposite).

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 like `create_page` or `update_page`. The description lacks context about prerequisites (e.g., page must exist) or post-publish behavior.

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