Skip to main content
Glama

Website: remove photos

website_photos_remove
Destructive

Delete photos stored for a client's new website, by their addresses (website_photos lists them). Only that site's own photos; a page still showing one needs website_save without it.

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": {
      "client": "<client>",
      "urls": "<urls>"
    },
    "name": "website_photos_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes
clientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds non-obvious behavior beyond that: removal is scoped to one site's own photos, and deleting a photo does not automatically update pages that reference it — the caller must re-save via website_save. It stops short of stating irreversibility or what happens to still-referenced photos.

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 tight sentences with the action front-loaded and zero filler. The second sentence is telegraphic to the point of being slightly cryptic ('needs website_save without it'), which costs a little clarity.

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, two-parameter mutation with no output schema, the definition covers the address source and the necessary follow-up save, which is the critical gap. It omits permanence/reversibility, limits on batch size behavior, and permission requirements, so it is adequate rather than complete.

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 0%, so the description has to carry parameter meaning. It clarifies that 'urls' are photo addresses and points to website_photos as their source, but says nothing about the 'client' parameter's format, the 1–50 item bounds, or error behavior on unknown addresses. Useful but only partially compensating for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Delete photos stored for a client's new website') and states the scoping rule ('Only that site's own photos'), which distinguishes it from website_photos (listing) and website_photos_copy. An agent can tell exactly what this tool does without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names website_photos as the way to obtain the addresses to pass in, and gives a follow-up rule: a page still showing a photo requires website_save without it. That is real workflow guidance, but there are no explicit when-not-to-use conditions (e.g., versus copy or list) and no note on prerequisite permissions.

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.