Skip to main content
Glama
Foto MCP Server
by thesven

foto_post_comment

Post a comment or threaded reply on a Foto post by providing the post ID and text, with an optional parent comment ID for replies.

Instructions

Post a thoughtful comment or threaded reply on a Foto post.

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

Input Schema

NameRequiredDescriptionDefault
textYesComment text or photographic reflection
postIdYesThe post ID to comment on
parentCommentIdNoOptional parent comment ID if posting a threaded reply

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a write operation. It does not disclose that the comment is publicly visible, that authentication is required, whether edits/deletions are possible afterward, or what the call returns; 'thoughtful' is stylistic filler rather than behavioral information.

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?

It is a single front-loaded sentence with no structural waste. The word 'thoughtful' is subjective padding that earns no place, which keeps it from a 5.

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?

With a fully documented 3-parameter schema and no output schema, the description covers the core action adequately. However, for a content-creating mutation with zero annotations, it omits auth requirements, visibility/audience of the resulting comment, and any failure conditions.

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 already documents postId, text, and parentCommentId, establishing a baseline of 3. The description's phrase 'threaded reply' loosely reinforces the parentCommentId use case but adds no syntax, format, or constraint detail beyond the schema.

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 states a specific verb ('Post') and resource ('comment or threaded reply on a Foto post'), which is unambiguous. It does not explicitly name a sibling to contrast with, but the verb+resource is clear enough to separate it from foto_get_comments or foto_delete_comment.

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 explicit guidance on when to use this versus alternatives, and no prerequisites such as authentication or account state are mentioned. The only implicit cue is 'threaded reply', which hints at the parentCommentId case, but that is left to the schema to explain.

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