list_public_pagesList active public pages owned by the authenticated workspace without password hashes or private URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| pages | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral detail beyond those flags: results are limited to active pages, and password hashes/private URLs are deliberately omitted from the response.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler. Key qualifiers—active, public, owned by authenticated workspace, and excluded fields—are packed efficiently without repeating annotation information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a low-complexity, zero-parameter read operation with a full output schema and rich annotations. The description covers what is listed, whose pages are listed, and what sensitive data is excluded, so nothing essential is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is empty with 100% coverage, so the description has no parameter documentation burden. The baseline for a zero-parameter tool is 4, and the description correctly focuses on output scope instead.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a precise action and resource: listing active public pages owned by the authenticated workspace, and explicitly excludes password hashes and private URLs. This scope distinguishes it from siblings like list_shared_with_me and search_workspace.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear usage context: it is appropriate for retrieving the authenticated workspace's own active public pages. It does not explicitly name alternatives or state when not to use it, but the ownership and active-page scope make the intended use unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target a distinct resource and action, and lifecycle pairs like publish_note_listing vs publish_media_listing or get_note vs get_collaboration_note are separated by clear wording. A few near-pairs such as move_file vs move_workspace_item and trash_file vs trash_workspace_item could still cause an agent to pick the wrong tool without careful reading.
All 38 tools follow one consistent verb_noun snake_case pattern with no camelCase or mixed conventions. Even less common verbs like upsert, trash, purge, and validate are applied uniformly, making the tool set predictable.
38 tools is well above the 25+ threshold and makes the overall surface feel heavy for tool selection. The number is defensible given the broad workspace, collaboration, and marketplace scope, but as a single MCP server it is not especially well-scoped.
The tool set covers workspace content lifecycle, collaboration, public pages, marketplace listings, Stripe seller flow, and agent registration without major dead ends. Minor gaps exist, such as no permanent delete outside of the trash flow and no direct collaboration-note deletion, but core workflows are supported.