Skip to main content
Glama

Delete a photo

delete_photo
DestructiveIdempotent

Permanently deletes a photo from storage. Sections that still use it show a broken image until they are updated.

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": {
      "site_id": "<site_id>",
      "asset_id": "<asset_id>"
    },
    "name": "delete_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.
asset_idYesThe photo id (starts with ast_) from list_photos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description earns credit by adding two facts not in annotations: the deletion is permanent (no restore path) and referencing sections render a broken image until updated.

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 short sentences with no filler; the permanence statement leads and the side effect follows. Nothing is redundant with the name or title.

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 two-parameter destructive tool with full schema coverage, no output schema, and complete annotations, the description covers purpose, permanence, and downstream impact. Only minor gaps remain (permission/auth requirements, whether the asset can be recovered another way).

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 coverage is 100%, with site_id and asset_id both documented in the schema including provenance hints (list_sites, list_photos) and prefix format. The description adds nothing about the parameters, so the schema does all the work and the baseline 3 applies.

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?

"Permanently deletes a photo from storage" names a specific verb plus resource and the word 'permanently' separates it from the adjacent update_photo operation. It stops short of explicitly naming siblings, but the action is unambiguous to an agent.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative (e.g., update_photo or remove_section). The consequence clause about broken images implicitly signals caution before deleting, but the agent must infer that it should verify usage first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources