Maps Agent

List published pages

list_articles

Read-onlyIdempotent

What Maps Agent has published, newest first. Without a form: how many pages each form has. With a form: its pages with title, summary, topic, date and URL, optionally narrowed by a topic word (an answer cluster such as 'reviews', a trade such as 'dentists', a guide kind such as 'template').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

Name	Required	Description
`form`	No	answer = one question answered first; guide = long reads, troubleshooting and copyable templates; research = our own measurements and statistics with method; glossary = terms; blog = articles; industry = what changes trade by trade; comparison = Maps Agent against other options; changelog = dated Google Business Profile changes.
`limit`	No	Page size (default 25, at most 100).
`topic`	No	A word to narrow by topic or title, e.g. 'reviews', 'suspension', 'dentists'.
`offset`	No	How many to skip, for paging (default 0).

Output Schema

Name	Required	Description
`form`	No
`forms`	No	Without a form: how many pages each form has.
`topic`	No
`total`	No	Pages in the form (after the topic filter).
`offset`	No
`results`	No	Newest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "form": {
+      "type": "string"
+    },
+    "forms": {
+      "description": "Without a form: how many pages each form has.",
+      "items": {
+        "properties": {
+          "count": {
+            "type": "integer"
+          },
+          "form": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "form",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "offset": {
+      "type": "integer"
+    },
+    "results": {
+      "description": "Newest first.",
+      "items": {
+        "properties": {
+          "form": {
+            "description": "The page's form.",
+            "enum": [
+              "answer",
+              "guide",
+              "research",
+              "glossary",
+              "blog",
+              "industry",
+              "comparison",
+              "changelog",
+              "page"
+            ],
+            "type": "string"
+          },
+          "slug": {
+            "description": "Its slug inside the form.",
+            "type": "string"
+          },
+          "summary": {
+            "description": "One or two plain sentences: the page's description or opening.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "The page title.",
+            "type": "string"
+          },
+          "topic": {
+            "description": "Grouping inside the form: answer cluster, guide kind, trade, blog vertical.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated": {
+            "description": "The page's own last-updated day, YYYY-MM-DD.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "The page on maps-agent.com — cite it.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "form",
+          "slug",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "topic": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "description": "Pages in the form (after the topic filter).",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are ordered newest first, the no-form case returns aggregate counts per form rather than pages, and the with-form case returns a defined field set. It does not discuss pagination limits or total counts, which keeps it below a 5.

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?

Two sentences, front-loaded with the core identity and ordering, then branching into the two modes. Every clause carries information; the nested parenthetical of topic examples is slightly dense but not wasteful.

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?

With an output schema present, return values do not need explaining, and annotations cover the safety profile. The description still discloses ordering, both modes and result fields, leaving only minor gaps such as paging expectations and whether totals are reported.

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?

Schema coverage is 100%, so the schema already defines form enum values, limit, offset and topic. The description still adds meaning beyond it by explaining the mode-switching semantics of form (counts without it, pages with it) and by characterizing what kind of word topic accepts (an answer cluster, a trade, a guide kind) rather than just 'a word'.

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 gives a concrete verb-and-resource ('What Maps Agent has published, newest first') and then spells out two distinct response modes depending on whether a form is supplied. It does not explicitly name a sibling such as get_article or search_knowledge, so the differentiation is behavioral rather than explicit, but an agent can still tell what this tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the mode split: omit form to get per-form counts, supply a form to get its pages. There is no explicit when-to-use versus get_article or search_knowledge, and no statement of when this is the wrong choice, so the agent must infer the alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Maps Agent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.