Skip to main content
Glama
lindoai

mcp-lindoai

Official

delete_blog

Destructive

Delete a blog post from a website by providing the website ID and blog post ID.

Instructions

Delete a blog post from a website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
website_idYesThe website ID
blog_idYesThe blog post ID to delete

Implementation Reference

  • The tool 'delete_blog' is registered using server.tool(). The schema defines two required parameters: website_id and blog_id. The handler makes a DELETE API call to /v1/workspace/website/{website_id}/blogs/{blog_id} and returns the result as JSON text.
    server.tool(
      "delete_blog",
      "Delete a blog post from a website.",
      {
        website_id: z.string().describe("The website ID"),
        blog_id: z.string().describe("The blog post ID to delete"),
      },
      { title: "Delete Blog Post", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ website_id, blog_id }) => {
        const data = await apiCall(`/v1/workspace/website/${website_id}/blogs/${blog_id}`, "DELETE");
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • The handler function for delete_blog: takes website_id and blog_id, performs a DELETE request to the API endpoint, 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}`, "DELETE");
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • Input schema for delete_blog: requires website_id (string) and blog_id (string) as parameters.
    {
      website_id: z.string().describe("The website ID"),
      blog_id: z.string().describe("The blog post ID to delete"),
    },
Behavior3/5

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

Annotations already indicate destructiveHint=true, so the description doesn't need to reiterate destruction. However, it adds no further behavioral details (e.g., irreversibility, cascading effects). The bar is lowered by annotations, so a score of 3 is appropriate.

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 extraneous words, perfectly concise for a simple delete operation.

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 destructive action with two well-documented parameters and no output schema, the description is adequate. It covers the core purpose, though it could mention permanence or side effects. Annotations help fill gaps.

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 descriptions for both parameters. The tool description adds no additional meaning beyond what the schema already provides, which meets the baseline but does not enhance understanding.

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 clearly states the action 'Delete' and the resource 'blog post from a website,' which is specific and distinct from sibling tools like update_blog or unpublish_blog.

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 (e.g., unpublish_blog) or any prerequisites or consequences. It lacks explicit context for appropriate usage.

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