Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

atlassian-mcp__confluence_get_comments

Read-only

Get all comments on a Confluence page, footer and inline, with their replies, including their body content and version info. Each comment carries its type (footer or inline) and parent_id, the comment it replies to, or null for a comment on the page itself. An inline comment also carries the page text it is anchored to and whether it is open or resolved.

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": {
      "page_id": "<page_id>"
    },
    "name": "atlassian-mcp__confluence_get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
page_idYesThe ID of the page whose comments to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, so the description's contribution is the return-shape disclosure: comment type, parent_id/reply threading, body content, version info, and inline anchor plus open/resolved state. That is genuinely useful context an agent could not get from annotations. It stops short of stating pagination behavior or maximum result size, which for an 'all comments' tool is the one meaningful remaining gap.

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?

Three sentences, front-loaded with the action and scope, then the threading semantics, then the inline-comment specifics. Every sentence conveys distinct information with no restatement of the tool name or filler.

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 two-parameter read tool with no output schema, the description does the heavy lifting by enumerating what each returned comment contains. Complete enough to call correctly and to interpret results, with only pagination/volume expectations missing.

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 page_id and account are already documented in structured fields. The description adds no extra meaning about parameter usage, such as whether page_id accepts a URL or only a numeric ID, or when a non-default account is needed. Baseline 3 applies because the schema carries this dimension.

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 gives a specific verb and resource ('Get all comments on a Confluence page') and immediately bounds the scope to footer and inline comments including replies. It does not name a sibling tool or state the read-vs-write contrast with confluence_add_comment, but the product and resource specificity is high enough that an agent can tell it apart from jira_get_comments and notion_get_comments.

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?

Usage is only implied by the verb 'Get' and by the mention that it returns all comments with replies, which hints that no per-comment loop is needed. There is no explicit when-to-use statement, no exclusion of cases (e.g. when you only need the page body, use confluence_get_page), and no stated prerequisites such as page read permission.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources