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

@growi/mcp-server

Official
by growilabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

addComment

Add a comment to a GROWI page by providing the page ID and comment text. Optionally specify the app name or revision ID.

Instructions

Add a comment to a page 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": {
      "pageId": "<pageId>",
      "comment": "<comment>"
    },
    "name": "addComment"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesID of the page to add a comment to
appNameNoGROWI app name to operate on (optional, uses default if not specified)
commentYesComment body text
revisionIdNoID of the revision to attach the comment to (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations indicate it is a write operation (readOnlyHint=false) but not destructive or idempotent. The description adds no extra behavioral context beyond the annotations, such as side effects or response behavior.

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 and easy to parse.

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?

For a simple creation tool, the description is adequate but does not cover return value or confirmation behavior. Given no output schema, additional context about the response would improve completeness.

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 fully documents parameters. The description does not add additional meaning beyond what the schema provides.

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 ('Add') and the resource ('comment to a page'), distinguishing it from sibling tools like removeComment and getComments. The verb-resource pair is specific and unambiguous.

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 like updating a comment (not available) or other operations. There is no discussion 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