Skip to main content
Glama
lindoai

mcp-lindoai

Official

get_blog

Read-only

Retrieve detailed information about a blog post by specifying the website ID and blog post ID.

Instructions

Get blog post details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
blog_idYesThe blog post ID

Implementation Reference

  • Registration of the 'get_blog' tool via server.tool() with the MCP server.
    server.tool(
      "get_blog",
      "Get blog post details.",
      {
        website_id: z.string().describe("The website ID"),
        blog_id: z.string().describe("The blog post ID"),
      },
      { title: "Get Blog Details", readOnlyHint: true, destructiveHint: false, openWorldHint: false },
      async ({ website_id, blog_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}`, "GET");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema: website_id (string) and blog_id (string) defined using Zod.
    {
      website_id: z.string().describe("The website ID"),
      blog_id: z.string().describe("The blog post ID"),
    },
  • Handler function that calls GET /v1/workspace/website/{website_id}/blogs/{blog_id} and returns results.
    async ({ website_id, blog_id }) => {
      const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}`, "GET");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • The apiCall helper used by the handler to make authenticated HTTP requests to the Lindo 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();
    }
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no additional behavioral context (e.g., auth requirements, rate limits, or what 'details' entails beyond schema).

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 sentence, no unnecessary words. Every word earns its place.

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?

No output schema, and the description does not specify what 'details' includes. For a simple get operation it may be adequate, but more specificity would improve 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 coverage is 100% with clear parameter descriptions. The tool description adds no additional meaning to the parameters, so baseline 3 is appropriate.

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 'Get blog post details.' clearly indicates a read operation on a specific resource (blog post). It distinguishes from getters for pages or websites, but 'details' is somewhat vague.

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 siblings like list_blogs or get_blog_html. No mention of prerequisites or alternatives.

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