Skip to main content
Glama
lindoai

mcp-lindoai

Official

update_blog

Update blog post metadata including name, URL path, and SEO settings for a specific website.

Instructions

Update blog post metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
blog_idYesThe blog post ID
nameNoBlog name
pathNoURL path
seoNoSEO settings object

Implementation Reference

  • Registration of the 'update_blog' tool using server.tool()
    server.tool(
      "update_blog",
      "Update blog post metadata.",
      {
        website_id: z.string().describe("The website ID"),
        blog_id: z.string().describe("The blog post ID"),
        name: z.string().optional().describe("Blog name"),
        path: z.string().optional().describe("URL path"),
        seo: z.record(z.unknown()).optional().describe("SEO settings object"),
      },
      { title: "Update Blog", readOnlyHint: false, destructiveHint: false, openWorldHint: false },
      async ({ website_id, blog_id, name, path, seo }) => {
        const body = {};
        if (name) body.name = name;
        if (path) body.path = path;
        if (seo) body.seo = seo;
        const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}`, "PATCH", body);
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for update_blog: website_id, blog_id, optional name/path/seo
    {
      website_id: z.string().describe("The website ID"),
      blog_id: z.string().describe("The blog post ID"),
      name: z.string().optional().describe("Blog name"),
      path: z.string().optional().describe("URL path"),
      seo: z.record(z.unknown()).optional().describe("SEO settings object"),
    },
  • Handler function that builds the request body and calls the PATCH API endpoint
    async ({ website_id, blog_id, name, path, seo }) => {
      const body = {};
      if (name) body.name = name;
      if (path) body.path = path;
      if (seo) body.seo = seo;
      const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}`, "PATCH", body);
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • The apiCall helper function used by the handler to make HTTP requests
    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 indicate readOnlyHint=false and destructiveHint=false, so the description needs to add behavioral context beyond that. However, it only says 'Update blog post metadata' without disclosing side effects (e.g., whether optional fields are overwritten or merged), required permissions, or whether the operation is reversible. The description adds no value beyond the annotations.

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, front-loaded sentence with no unnecessary words. It efficiently states the tool's purpose. Every word earns its place.

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

Completeness2/5

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

The tool has 5 parameters (2 required) and no output schema. The description does not cover what the return value looks like, the behavior of optional fields when omitted (e.g., unchanged vs cleared), or error conditions. Given the write nature and nested object parameters, the description is too brief to fully inform the agent.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema already documents each field. The description 'metadata' hints that name, path, and seo are metadata fields, but this is redundant with the schema. Baseline 3 is appropriate since the description adds minimal extra meaning.

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 'Update blog post metadata' clearly specifies the action (update) and the resource (blog post metadata). It distinguishes this tool from siblings like create_blog (creation), delete_blog (deletion), and update_blog_content (which likely updates content, not metadata). The verb+resource is precise and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_blog, update_blog_content, publish_blog, etc. It does not mention prerequisites, exclusions, or typical use cases, leaving the agent to infer usage from the name alone.

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