Skip to main content
Glama

Remove a photo

remove_photo
Destructive

Deletes one photo (of a unit or of the venue) for good. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "photo_id": "<photo_id>"
    },
    "name": "remove_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
photo_idYesId of the photo.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description's 'for good' merely reinforces permanence rather than adding new behavioral information. It does note the operation is scoped to one venue addressed by address plus access key, which is useful context, but it says nothing about a confirmation step, cascade effects (e.g. deleting the cover photo), or what happens when the photo_id does not exist.

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 short sentences, front-loaded with the action and its permanence, with no filler. The second sentence largely restates required parameters already documented in the schema, which keeps it from being maximally efficient.

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 simple single-object destructive tool with full annotation coverage, full schema coverage, and no output schema, the description conveys what is deleted, that it is permanent, and the venue scoping. Only secondary edge cases (missing photo_id, effect on cover photo) are omitted.

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 address, photo_id, and access_key are all documented in the schema; the description only restates that address and access key are the venue identifiers. It adds no format, ID-source, or constraint detail beyond the schema, so the baseline of 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?

States a specific verb ('Deletes') and resource ('one photo'), plus the scope variants (of a unit or of the venue) so the agent knows exactly which object is affected. It does not name the sibling set_cover_photo or distinguish itself from a hypothetical bulk photo removal, so it stops short of full sibling differentiation.

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?

Usage is only implied: 'Deletes one photo... for good' plus 'Acts on one venue' tells the agent the granularity is a single photo at a single venue, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. set_cover_photo for replacing the cover image rather than deleting).

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