Skip to main content
Glama
Sign In
@growi/mcp-server

@growi/mcp-server

Official
by growilabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pageListingInfo

Read-onlyIdempotent

Retrieve summary information for GROWI pages by providing page IDs or a page path.

Instructions

Get summary information for pages in GROWI by IDs or path

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": "pageListingInfo"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath of the page to get summary information for (One of `pageIds` or `path` must be provided)
appNameNoGROWI app name to operate on (optional, uses default if not specified)
pageIdsNoArray of page IDs to get summary information for (One of `pageIds` or `path` must be provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds minimal behavioral context beyond stating it returns 'summary information', which is already implied by the name.

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

Conciseness5/5

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

The description is a single, concise sentence with no wasted words. It is front-loaded with the core action.

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

Completeness3/5

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

While the tool is simple and has no output schema, the description omits details about the structure or content of the 'summary information', which could help the agent understand what to expect.

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 description coverage is 100%, so the schema already explains the parameters. The description's mention of 'by IDs or path' aligns with the schema but does not add extra meaning.

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 clearly states the action ('Get summary information'), the resource ('pages'), and the input method ('by IDs or path'). However, it does not explicitly differentiate from sibling tools like getPage or getPageInfo, which may return full content.

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?

The description provides no guidance on when to use this tool versus alternatives like getPage or getPageInfo. No mention of prerequisites or context.

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