Skip to main content
Glama
Sign In

PubSpace

by ai.pubspace
OverviewDiscussionsAdmin

Read comments on a page

list_comments
Read-onlyIdempotent

Read the comments people left on a page: { page_id, url, commentsEnabled, threads: [{ id, resolved, on, comments: [{ id, author, body, createdAt }] }] }. Each thread is a pin someone dropped on the page; on is the text of the element they clicked, so you can tell what the comment is about without seeing the page. author is the commenter's full email. Read-only. Typical loop: list_comments → update_page with the fixes → resolve_comment on each thread you addressed. Open threads only unless include_resolved is true. Fails with page_not_found if the id is not in this space.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page_id": "<page_id>"
    },
    "name": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesThe page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible.
include_resolvedNoDefault false. true also returns resolved threads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds substantial context beyond them: the shape of the returned threads, the meaning of the `on` field (the text of the clicked element), that author is a full email, the default resolution filter, and the page_not_found failure mode for out-of-space ids.

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?

Front-loads the purpose and returned structure, then moves to semantics, workflow, filtering, and error behavior. Slightly dense and includes a minor redundancy ('Read-only' is already in annotations), but every sentence carries usable information.

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

Completeness5/5

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

With no output schema, the description takes on the burden of describing the return shape and does so precisely, including nested thread/comment fields. It also covers filtering defaults and the primary failure mode, leaving nothing an agent needs before calling it.

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% and both parameters are already documented in the schema, including the scope restriction on page_id. The description reinforces the include_resolved default behavior but adds no syntax or format detail beyond what the schema provides, so this is the baseline case.

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?

States a specific verb and resource ('Read the comments people left on a page') and the scope implied by the returned structure, which clearly separates it from siblings like resolve_comment, set_comments, and get_page. An agent can identify the tool's function without opening the schema.

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

Usage Guidelines4/5

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

Provides a concrete workflow ('list_comments → update_page with the fixes → resolve_comment on each thread you addressed') that tells the agent where this tool sits in a sequence, and specifies the default filter (open threads only unless include_resolved is true). It does not explicitly exclude alternatives such as get_page, but the surrounding context is clear.

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

All PubSpace toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources