Skip to main content
Glama
Moe03

Google Maps MCP Server

by Moe03

get_posts

Retrieve location-based posts from Google Maps to access user reviews, photos, and updates for places of interest.

Instructions

Retrieves all posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that executes the get_posts tool logic. Logs the number of posts and returns a JSON string of all posts.
    async function handleGetPosts() {
      console.error(`Handling get_posts request, found ${posts.length} posts`);
      
      return {
        content: [{ 
          type: "text", 
          text: JSON.stringify(posts, null, 2)
        }],
        isError: false,
      };
    }
  • Tool schema definition with name, description, and empty input schema (no parameters required).
    const GET_POSTS_TOOL: Tool = {
      name: "get_posts",
      description: "Retrieves all posts.",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    };
  • src/index.ts:77-82 (registration)
    Registration of the get_posts tool (as GET_POSTS_TOOL) in the array of tools returned by the ListTools handler.
    const SIMPLE_TOOLS = [
      GET_WEATHER_TOOL,
      ADD_POST_TOOL,
      GET_POSTS_TOOL,
      DELETE_POST_TOOL,
    ] as const;
  • src/index.ts:191-193 (registration)
    Dispatch/registration of get_posts tool call to the handleGetPosts handler in the CallToolRequestSchema switch statement.
    case "get_posts": {
      return await handleGetPosts();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'retrieves' implying a read operation, but doesn't disclose behavioral traits like whether it's paginated, sorted, filtered, or has rate limits. For a read tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence 'Retrieves all posts', which is appropriately concise and front-loaded. There's no wasted text, though it could be slightly more informative without sacrificing brevity.

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 simplicity (0 params, no output schema, no annotations), the description is incomplete. It doesn't explain what 'posts' are, the return format, or any constraints, leaving the agent with insufficient context to use it effectively beyond basic inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description doesn't add param details, which is appropriate, earning a baseline score of 4 for not misleading or omitting necessary param semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Retrieves all posts' clearly states the action (retrieves) and resource (posts), but it's vague about scope and doesn't differentiate from sibling tools like 'get_weather' which might also retrieve data. It's not tautological but lacks specificity about what 'all posts' means.

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 is provided on when to use this tool versus alternatives like 'add_post' or 'delete_post'. The description doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names 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/Moe03/mcp-hello-world'

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