Skip to main content
Glama
lindoai

mcp-lindoai

Official

unpublish_page

Destructive

Unpublish a page to take it offline, removing it from public access on your website.

Instructions

Unpublish a page from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
page_idYesThe page ID to unpublish

Implementation Reference

  • The handler function for the 'unpublish_page' tool. It calls the API endpoint to unpublish a page 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, null, 2) }] };
    }
  • Input schema for 'unpublish_page' tool: website_id (string) and page_id (string).
    {
      website_id: z.string().describe("The website ID"),
      page_id: z.string().describe("The page ID to unpublish"),
    },
  • Registration of the 'unpublish_page' tool using server.tool() with metadata (title, destructiveHint, etc.) and the handler.
    server.tool(
      "unpublish_page",
      "Unpublish a page from a website.",
      {
        website_id: z.string().describe("The website ID"),
        page_id: z.string().describe("The page ID to unpublish"),
      },
      { title: "Unpublish Page", 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, null, 2) }] };
      }
    );
  • The apiCall helper function used by the handler 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?

The annotations declare destructiveHint: true, which already informs the agent that the tool is destructive. The description adds no further behavioral context, such as whether the page becomes a draft or if it requires certain permissions. The description is adequate given the annotations but does not go beyond them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single short sentence, which is concise but may be too brief. It lacks front-loaded key details like the effect of unpublishing, which would make it more useful. The structure is acceptable but not exemplary.

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?

The description does not explain what happens after unpublishing (e.g., the page becomes inaccessible or reverts to draft), nor does it mention any side effects or required page state. Given the tool's destructive nature and lack of output schema, more context would help an agent use it correctly.

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 already describes both parameters clearly with 100% coverage, so the description does not need to add much. The description does not explain the meaning beyond the schema, such as how to obtain website_id or page_id, but the schema itself is sufficient.

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 verb 'Unpublish' and the resource 'a page from a website', which makes the tool's purpose immediately understandable. However, it does not differentiate from similar sibling tools like 'delete_page' or 'publish_page', which could cause confusion for an AI agent.

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, such as 'delete_page' for permanent removal or 'publish_page' for the reverse action. The description does not mention any prerequisites, like the page needing to be published first, or consequences of unpublishing.

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