@growi/mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

getUserRecentPages

Read-onlyIdempotent

Retrieve recently created pages by a specific user in GROWI, enabling AI to access their contributions for context-aware responses.

Instructions

Get recently created pages by a specific user in GROWI

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": {
      "id": "<id>"
    },
    "name": "getUserRecentPages"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	User ID to get recent pages for
`appName`	No	GROWI app name to operate on (optional, uses default if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1May 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the read-only nature is clear. The description adds context about user specificity but does not detail behavior like error handling, return format, or pagination. No contradiction with annotations.

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 sentence that efficiently conveys the tool's purpose. Every word is meaningful, and there is no superfluous text.

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

Completeness2/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 should mention what the tool returns (e.g., list of pages, metadata). It also omits details like ordering, limits, or error conditions. Given the complexity of sibling tools, more context would be beneficial.

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%, so the schema already documents both parameters. The description mentions 'specific user' which aligns with the 'id' parameter but adds no additional meaning beyond the schema descriptions.

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?

The description clearly states the action (get), the resource (recently created pages), and the scope (by a specific user). It distinguishes from sibling tools like getRecentPages (all users) and getPage (single page).

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?

No guidance is provided on when to use this tool versus alternatives such as getRecentPages, getPage, or other user-specific tools. The description does not mention exclusions or prerequisites.

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