Skip to main content
Glama
Sign In
dev.mcp

dev.mcp

by iwilldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

confluence_get_page_inline_comments

Retrieve inline comments for a Confluence page by providing its page ID. Use optional limit and cursor to paginate through large sets of comments.

Instructions

Inline comments (GET /wiki/api/v2/pages/{id}/inline-comments).

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>"
    },
    "name": "confluence_get_page_inline_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
pageIdYesPage ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are present, so the description has full responsibility for disclosing behavior. It reveals only the HTTP method and path; it does not mention pagination, response shape, ordering, or whether only comments visible to the user are returned. This is minimal disclosure.

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?

The description is very short and front-loaded, with no filler. However, it may be too terse to fully support call construction.

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 or annotations, the description would need to state what the response contains and how pagination works. It does neither, so the definition is incomplete for correct invocation beyond the minimal pageId call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema describes only pageId ('Page ID.'), and the inferred endpoint confirms this parameter. limit and cursor have no descriptions, and the description does not explain their role in pagination, leaving 67% of parameters underspecified.

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 identifies the operation as retrieving inline comments for a page and gives the exact REST endpoint, so an agent can infer the resource and HTTP verb. It is clear, though it doesn't explicitly state 'list' or differentiate from the footer-comments sibling beyond the path.

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?

There is no guidance on when to choose this over alternatives like confluence_get_page_footer_comments or confluence_create_inline_comment. The name and endpoint hint at the use case, but no explicit context or exclusions are given.

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