Skip to main content
Glama
Moe03

Google Maps MCP Server

by Moe03

delete_post

Remove a Google Maps post by specifying its ID to manage location-based content.

Instructions

Deletes a post by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the post to delete.

Implementation Reference

  • The handler function that implements the delete_post tool logic: searches for post by ID in the in-memory posts array, removes it if found, and returns appropriate success or error response.
    async function handleDeletePost(id: string) {
      console.error(`Handling delete_post request for ID: ${id}`);
      
      const initialLength = posts.length;
      const postIndex = posts.findIndex(post => post.id === id);
      
      if (postIndex === -1) {
        return {
          content: [{ type: "text", text: `Error: No post found with ID: ${id}` }],
          isError: true,
        };
      }
      
      posts.splice(postIndex, 1);
      
      return {
        content: [{ type: "text", text: `Success! Post with ID: ${id} deleted.` }],
        isError: false,
      };
    }
  • Tool definition including schema for delete_post: requires 'id' as string input.
    const DELETE_POST_TOOL: Tool = {
      name: "delete_post",
      description: "Deletes a post by ID.",
      inputSchema: {
        type: "object",
        properties: {
          id: {
            type: "string",
            description: "The ID of the post to delete.",
          },
        },
        required: ["id"],
      },
    };
  • src/index.ts:77-82 (registration)
    Registration of delete_post tool (DELETE_POST_TOOL) in the array of tools advertised via listTools endpoint.
    const SIMPLE_TOOLS = [
      GET_WEATHER_TOOL,
      ADD_POST_TOOL,
      GET_POSTS_TOOL,
      DELETE_POST_TOOL,
    ] as const;
  • src/index.ts:195-198 (registration)
    Dispatch logic in CallToolRequest handler switch statement that routes delete_post calls to the handleDeletePost function.
    case "delete_post": {
      const { id } = request.params.arguments as { id: string };
      return await handleDeletePost(id);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a post, implying a destructive mutation, but fails to mention critical details such as whether deletion is permanent or reversible, what permissions are required, or what happens to associated data. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with a single, direct sentence that front-loads the core action ('Deletes a post by ID'). There is no wasted language or unnecessary elaboration, making it efficient and easy to parse.

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?

Given the tool's complexity (a destructive operation with no annotations and no output schema), the description is incomplete. It lacks information on behavioral traits (e.g., permanence, side effects), usage context, and expected outcomes, which are crucial for an AI agent to invoke this tool correctly and safely.

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 description mentions 'by ID', which aligns with the single parameter 'id' in the input schema. Since schema description coverage is 100% (the schema fully documents the parameter), the description adds minimal value beyond restating what's already in the schema. This meets the baseline for adequate but not enhanced parameter semantics.

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 clearly states the action ('Deletes') and the resource ('a post by ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'add_post' or 'get_posts' beyond the obvious verb difference, missing an opportunity to clarify its specific role in the CRUD operations context.

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 like 'add_post' or 'get_posts', nor does it mention prerequisites (e.g., needing an existing post ID) or consequences. It simply states what the tool does without contextual usage instructions.

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/Moe03/mcp-hello-world'

If you have feedback or need assistance with the MCP directory API, please join our Discord server