Skip to main content
Glama
lindoai

mcp-lindoai

Official

update_page_content

Update an existing webpage by replacing its HTML content. Modify page content and SEO settings for any page on your website.

Instructions

Update the content of an existing page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
page_idYesThe page ID
page_contentYesUpdated page content in HTML
seoNoSEO settings object

Implementation Reference

  • Registration of the 'update_page_content' tool via server.tool() with name, description, and metadata.
    server.tool(
      "update_page_content",
      "Update the content of an existing page.",
      {
        website_id: z.string().describe("The website ID"),
        page_id: z.string().describe("The page ID"),
        page_content: z.string().describe("Updated page content in HTML"),
        seo: z.record(z.unknown()).optional().describe("SEO settings object"),
      },
      { title: "Update Page Content", readOnlyHint: false, destructiveHint: false, openWorldHint: true },
      async ({ website_id, page_id, page_content, seo }) => {
        const body = { page_content };
        if (seo) body.seo = seo;
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/update`, "POST", body);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema defining required parameters: website_id (string), page_id (string), page_content (string - HTML), and optional seo (record).
    {
      website_id: z.string().describe("The website ID"),
      page_id: z.string().describe("The page ID"),
      page_content: z.string().describe("Updated page content in HTML"),
      seo: z.record(z.unknown()).optional().describe("SEO settings object"),
    },
  • Handler function that constructs the request body with page_content (and optionally seo), then calls the API endpoint POST /v1/workspace/website/{website_id}/pages/{page_id}/update.
    async ({ website_id, page_id, page_content, seo }) => {
      const body = { page_content };
      if (seo) body.seo = seo;
      const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/update`, "POST", body);
      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 indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds no additional behavioral context such as whether content is replaced or appended, or any side effects.

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?

The description is a single sentence that is both concise and front-loaded. No unnecessary words.

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?

The description is adequate for a simple update tool, but lacks differentiation from siblings and does not mention return value or error conditions. Given the presence of many sibling tools, more context would be helpful.

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 the baseline is 3. The description adds no parameter-specific details beyond what the schema already provides.

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 states 'Update the content of an existing page' which clearly identifies the verb and resource. However, it does not distinguish from the sibling 'update_page' tool, which may have overlapping functionality.

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 'update_page' or 'update_blog_content'. There is no mention of prerequisites or context.

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