Skip to main content
Glama
lindoai

mcp-lindoai

Official

Unpublish Page

unpublish_page
Destructive

Unpublish a page from a website by specifying its website ID and page ID.

Instructions

Unpublish a page from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
page_idYesThe page ID to unpublish

Implementation Reference

  • Registration of the 'unpublish_page' tool using server.registerTool() with its name, metadata, input schema, and handler callback.
    server.registerTool(
      "unpublish_page",
      {
        title: "Unpublish Page",
        description: "Unpublish a page from a website.",
        inputSchema: {
        website_id: z.string().describe("The website ID"),
        page_id: z.string().describe("The page ID to unpublish"),
      },
        annotations: { readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      },
      async ({ website_id, page_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/unpublish`, "POST");
        return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
      }
    );
  • Input schema for unpublish_page: requires website_id (string) and page_id (string), validated with Zod.
      inputSchema: {
      website_id: z.string().describe("The website ID"),
      page_id: z.string().describe("The page ID to unpublish"),
    },
  • Handler function that calls apiCall to POST to /v1/workspace/website/{website_id}/pages/{page_id}/unpublish and returns the result.
      async ({ website_id, page_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/unpublish`, "POST");
        return { content: [{ type: "text", text: JSON.stringify(data?.result ?? data, null, 2) }] };
      }
    );
  • The apiCall helper function that the unpublish_page handler uses to make authenticated HTTP requests to the backend 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();
    }
Behavior3/5

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

Annotations (destructiveHint=true) already indicate destructive nature. Description adds 'Unpublish' which implies state change but doesn't elaborate on reversibility or side effects. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no fluff. Could be slightly more informative, but acceptable for a simple tool.

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?

Minimally adequate given annotations and simple schema. Lacks behavioral details like impact on visibility or reversibility.

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 description does not need to add parameter details. It adds no additional meaning beyond what 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 (unpublish) and resource (page), adding context ('from a website') that distinguishes it from sibling tools like publish_page or delete_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 on when to unpublish versus delete or other alternatives. Lacks prerequisites (e.g., page must be published) and context for appropriate 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/lindoai/mcp-server'

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