Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_page_html

Read-only

Retrieve the raw HTML content of a specific page on a website by providing the website and page IDs.

Instructions

Get the HTML content of a page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
page_idYesThe page ID

Implementation Reference

  • Registration and handler for the 'get_page_html' tool. Registered via server.tool() with schema (website_id, page_id) and handler that makes a GET API call to retrieve the HTML content of a page.
    server.tool(
      "get_page_html",
      "Get the HTML content of a page.",
      {
        website_id: z.string().describe("The website ID"),
        page_id: z.string().describe("The page ID"),
      },
      { title: "Get Page HTML", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async ({ website_id, page_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/html`, "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for get_page_html: requires website_id and page_id as strings.
    {
      website_id: z.string().describe("The website ID"),
      page_id: z.string().describe("The page ID"),
    },
  • The handler function that calls the API endpoint to fetch the HTML content of the specified page and returns it as text content.
    async ({ website_id, page_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/pages/${page_id}/html`, "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Helper function for making authenticated API calls to the Lindo AI backend.
    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 already indicate readOnlyHint=true, so the description adds minimal behavioral context. It does not disclose potential constraints like HTML size limits or formatting details.

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, clear sentence with no unnecessary words. Front-loaded and efficient.

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?

Given the low complexity (2 simple parameters, no output schema) and annotations covering safety, the description is adequate. However, it could mention the return format (e.g., HTML string) or error handling.

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 description coverage is 100%, so the description adds no additional meaning beyond the schema's parameter descriptions. Baseline score of 3 is appropriate.

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?

Clearly states it gets HTML content of a page, distinguishing it from sibling tools like 'get_page' (which likely returns metadata) and 'get_blog_html' (for blogs).

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 use this tool versus alternatives like 'get_page' or 'get_page_content'. The description lacks context on when this tool is appropriate.

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