Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_blog_html

Read-only

Get the full HTML content of a blog post by specifying the website ID and blog post ID.

Instructions

Get the HTML content of a blog post.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
blog_idYesThe blog post ID

Implementation Reference

  • Registration of the 'get_blog_html' tool with the MCP server, defining its schema (website_id and blog_id as strings) and handler that calls the API endpoint to fetch blog HTML content.
    server.tool(
      "get_blog_html",
      "Get the HTML content of a blog post.",
      {
        website_id: z.string().describe("The website ID"),
        blog_id: z.string().describe("The blog post ID"),
      },
      { title: "Get Blog HTML", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async ({ website_id, blog_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}/html`, "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Handler function for the 'get_blog_html' tool that makes a GET request to `/v1/workspace/website/${website_id}/blogs/${blog_id}/html` and returns the JSON response as text content.
    async ({ website_id, blog_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}/html`, "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for the 'get_blog_html' tool: requires `website_id` (string) and `blog_id` (string), validated with Zod.
    {
      website_id: z.string().describe("The website ID"),
      blog_id: z.string().describe("The blog post ID"),
    },
  • The `apiCall` helper function used by the tool handler to make authenticated HTTP requests to the Lindo AI 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 already declare readOnlyHint=true and destructiveHint=false, so the description adds minimal value by stating the obvious. No additional behavioral details (e.g., return format, size limits) are provided.

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 with no wasted words, front-loaded with the core action. It is appropriately sized for the tool's simplicity.

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?

For a simple read-only tool with annotations and clear parameters, the description is mostly complete. However, the absence of an output schema and lack of details about the HTML content returned slightly limit completeness.

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% with clear parameter descriptions. The description adds no further meaning beyond the schema, meeting the baseline expectation.

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 uses a specific verb ('Get') and resource ('HTML content of a blog post'), clearly distinguishing it from sibling tools like 'get_blog' (metadata) and 'get_page_html' (page HTML).

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 versus alternatives (e.g., 'get_blog'), no prerequisites or exclusions mentioned. The description lacks context for agent decision-making.

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