Skip to main content
Glama
Foto MCP Server
by thesven

foto_delete_post

Delete a published Foto post by post ID to remove its document, scrub slide metadata, update your profile, and prune tag shards.

Instructions

Delete a published post on Foto by post ID. Automatically removes the post document, scrubs all slide private metadata, updates your user profile, and prunes tag shards.

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_delete_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID of the post to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

B3.2/5.0
Behavior3/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. It does usefully enumerate cascading side effects (post document removal, private slide metadata scrub, profile update, tag shard pruning), which is real value beyond the name. However, it omits that deletion is irreversible, what permissions or ownership are required, and what happens to comments/likes on the post.

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?

Two sentences, front-loaded with the action and target, followed by the side-effect list. No padding beyond the mild filler 'on Foto'; every other clause conveys behavior.

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?

For a destructive mutation with no annotations and no output schema, the description covers the mechanics well but leaves out irreversibility, authorization/ownership requirements, and failure modes (e.g., nonexistent or unpublished post ID). Adequate but with clear gaps for a delete operation.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description adds only the phrase 'by post ID', which restates the schema rather than adding format, sourcing, or validation meaning.

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 ('Delete a published post') plus the identifier used ('by post ID'), which is enough to distinguish it from siblings operating on comments or portfolios. It stops short of explicitly contrasting with foto_update_post or explaining what 'published' excludes (drafts), so differentiation is implicit rather than stated.

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 when-to-use guidance: no prerequisites (must you be the post owner?), no confirmation or irreversibility note, and no mention of the alternative of unpublishing via foto_update_post. The agent is told what the tool does but not the conditions under which it should be chosen.

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