Skip to main content
Glama
Foto MCP Server
by thesven

foto_delete_comment

Delete a comment or threaded reply on a Foto post and decrement the post comment counter.

Instructions

Delete one of your comments or threaded replies on a Foto post and decrement the post comment counter.

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

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID the comment belongs to
isReplyNoSet to true if deleting a threaded reply from the replies collection
commentIdYesThe comment or reply ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add one genuinely non-obvious behavioral detail: the post comment counter is decremented as a side effect. It omits other important traits for a destructive operation, such as whether deletion is permanent, whether child replies are affected, and what authorization is required.

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 no filler: the action, the ownership scope, and the side effect all appear in order of importance. Nothing needs trimming or reordering.

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?

The input schema is fully self-documenting and no output schema exists, so the description only needs to add the action and side-effect context, which it does. The remaining gap is the absence of any irreversibility or permission framing for a delete operation, which would matter more if a response payload were expected.

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 are already documented in the schema, making 3 the baseline. The mention of "threaded replies" loosely corresponds to the isReply flag but adds no format or edge-case detail (e.g., what happens if isReply is omitted for a reply).

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 (delete) and a precisely scoped resource (your own comments or threaded replies on a Foto post), which separates it from sibling mutations like foto_delete_portfolio or foto_delete_post. It stops short of explicitly naming an alternative tool, so the differentiation is implied by resource rather than routed.

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?

Phrasing such as "one of your comments" implies an ownership precondition and a comment-targeted use case, which is useful context. However, there is no explicit when-to-use/when-not-to-use guidance, no statement of prerequisites or permissions, and no pointer to related tools such as foto_get_comments for locating a comment ID.

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