Skip to main content
Glama
Foto MCP Server
by thesven

foto_delete_portfolio

Delete a published portfolio showcase by post ID and automatically clean up its slide metadata, profile post references, and tag shards.

Instructions

Delete a published portfolio showcase on Foto by post ID. Cascades cleanup across all slide private metadata, user profile postIds, and 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_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe portfolio post ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it delivers real value: it discloses that deletion cascades across slide private metadata, user profile postIds, and tag shards, which an agent could not learn from the schema. It stops short of stating irreversibility, permission requirements, or behavior for a missing/invalid post ID.

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?

Two sentences, both front-loaded with the operation and its cascade effects, with zero filler or redundant restatement of the schema.

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 destructive single-parameter tool with no annotations and no output schema, the description covers purpose and the multi-area side effects well. It is only slightly incomplete on irreversibility and return/error behavior, which matters for an unrecoverable 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 one parameter at 100% schema coverage; the schema already documents postId as 'The portfolio post ID to delete,' so the description's 'by post ID' adds essentially nothing new. Baseline 3 applies when the schema does the heavy lifting.

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?

Names a specific verb and resource: 'Delete a published portfolio showcase on Foto by post ID.' That is unambiguous about what is removed. It does not, however, differentiate itself from the sibling foto_delete_post, which an agent could easily confuse for this same post.

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?

The qualifier 'published' implies that only published showcases can be deleted, which is useful implicit scoping, but there is no explicit when-to-use, when-not, or alternative routing against foto_delete_post, foto_update_portfolio, or foto_create_portfolio. An agent must infer selection criteria from the name alone.

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