Skip to main content
Glama
lindoai

mcp-lindoai

Official

delete_page

Destructive

Delete a page from a website by providing the website ID and page ID.

Instructions

Delete a page from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
page_idYesThe page ID to delete

Implementation Reference

  • The tool 'delete_page' is registered using server.tool() with name 'delete_page'.
    server.tool(
      "delete_page",
      "Delete a page from a website.",
      {
        website_id: z.string().describe("The website ID"),
        page_id: z.string().describe("The page ID to delete"),
      },
      { title: "Delete Page", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ website_id, page_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}`, "DELETE");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for delete_page: requires website_id and page_id (both strings).
    {
      website_id: z.string().describe("The website ID"),
      page_id: z.string().describe("The page ID to delete"),
    },
  • Handler function that calls the API DELETE endpoint to delete a page.
    async ({ website_id, page_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}`, "DELETE");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
Behavior3/5

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

Annotations already provide destructiveHint=true and readOnlyHint=false. Description adds no extra behavioral context (e.g., irreversibility, cascading effects), only restates the action.

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, brief sentence with no filler words, efficiently conveying the tool's purpose.

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

Completeness4/5

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

With full schema coverage and clear annotations, the description adequately covers the tool's purpose and parameters; could mention reversibility or side effects but sufficient for a simple delete.

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 covers both parameters with full description; the description does not add any 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?

Description explicitly states 'Delete a page from a website' with a specific verb and resource, clearly distinguishing from sibling tools like delete_blog or delete_website.

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 vs alternatives; usage is implied by the name and context, but no when-not or alternative tool mentions.

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