Skip to main content
Glama
Foto MCP Server
by thesven

foto_get_comments

Retrieve comments and nested threaded replies for a Foto post by post ID, with options to limit results and include or skip replies.

Instructions

Retrieve comments and nested threaded replies on a Foto post by post ID.

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": {
      "postId": "<postId>"
    },
    "name": "foto_get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum comments to retrieve (default: 20)
postIdYesThe post ID to get comments for
includeRepliesNoWhether to resolve threaded replies from the replies collection (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it. It never says whether authentication is required, how results are ordered or paginated, or what happens when includeReplies resolves replies; the threading detail it does mention is largely already in the schema.

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?

A single front-loaded sentence with zero filler; the resource and its scoping key arrive immediately.

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 three-parameter read tool with full schema coverage and no output schema, the core purpose is adequately conveyed. It is thin on return-value shape and auth expectations, but nothing essential to invoking it is 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 all three parameters (postId, limit, includeReplies) are already documented with defaults and bounds. The description adds no syntax, format, or edge-case meaning beyond the schema, which is the expected baseline.

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?

States a specific verb (retrieve) plus a specific resource (comments and nested threaded replies) scoped to a post ID, which clearly separates it from foto_post_comment and foto_delete_comment. It does not name any sibling explicitly, so it falls just short of a 5.

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 implied by 'on a Foto post by post ID', so an agent can infer this is the read-side counterpart to posting comments. There is no explicit when-to-use/when-not guidance and no mention of how it relates to foto_get_post or the like.

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