Skip to main content
Glama
lindoai

mcp-lindoai

Official

publish_page

Publish a static page on a website with HTML content, custom URL path, and SEO title.

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

  • Registration of the publish_page tool via server.tool() with its name, description, schema, metadata, and handler.
    server.tool(
      "publish_page",
      "Publish a static page with HTML content.",
      {
        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"),
      },
      { title: "Publish Page", 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, null, 2) }] };
      }
  • The async handler function for publish_page that constructs the request body (path, page_content, seo with page_title) and calls the API to create the page.
    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, null, 2) }] };
    }
  • Input schema for publish_page defining required parameters: website_id (string), path (string), page_content (string HTML), and page_title (string for SEO).
    {
      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"),
    },
    { title: "Publish Page", readOnlyHint: false, destructiveHint: false, openWorldHint: true },
  • The apiCall helper function used by the publish_page handler to make 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 only says 'Publish a static page with HTML content' without disclosing whether it creates a new page or publishes an existing one, or what side effects occur. Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no additional behavioral context beyond these annotations.

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?

The description is a single sentence, concise and to the point. It is front-loaded with the action and resource, but the brevity sacrifices critical details.

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?

Given the presence of sibling tools like create_page, update_page, and unpublish_page, the description lacks information about the publish lifecycle, prerequisites, and return behavior. The lack of an output schema is not compensated for by the description, making it incomplete for agent use.

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?

The input schema has 100% coverage with parameter descriptions. The tool description adds minimal value, only reiterating that the content is HTML. Since the schema already documents the parameters, a score of 3 is appropriate.

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 clearly states the action (publish) and resource (static page), and mentions HTML content. It distinguishes from sibling tools like create_page and unpublish_page, but does not explicitly clarify the lifecycle relationship (e.g., whether it creates or publishes an existing page).

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 is provided on when to use this tool versus alternatives like create_page or publish_blog. The description does not mention prerequisites, such as whether the page must already exist, leaving the agent to infer from sibling names.

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