Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List pages

list_pages
Read-only

List workspace pages with ID, name, slug and publish status, optionally filtered by a search string to quickly locate the page you need.

Instructions

List the workspace's pages (id, name, slug, published), optionally filtered by a search string.

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_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOptional text to filter pages by name or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.73.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by naming the fields returned, but says nothing about pagination, result limits, or ordering, which matter for a list operation.

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?

One compact sentence with the resource and returned fields front-loaded and no wasted wording. It could be marginally tighter, but every clause carries information.

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?

For a simple one-parameter read tool with annotations covering safety and no output schema, the description supplies the essential shape of the result set. Only pagination and ordering behavior are missing, which is a minor gap at this complexity.

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 the single search parameter is fully documented in the schema as filtering by name or slug. The description's "optionally filtered by a search string" restates that without adding syntax, matching behavior, or case-sensitivity details, so baseline 3 applies.

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?

States a specific verb and resource ("List the workspace's pages") and enumerates the returned fields (id, name, slug, published), which lets an agent distinguish it from a trashed-pages listing. It stops short of naming a sibling alternative explicitly, so it is clear but not fully differentiated.

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?

The optional search filter implies a use case, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of how this relates to list_trashed_pages or list_page_types. Usage must be inferred from the name and the word "workspace's".

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

Deploy Server

Other Tools