Skip to main content
Glama

Add a photo from a link

add_photo

Adds a photo to a unit, or to the venue itself when unit_id is left out. Give the direct public https link to an existing photo file (jpg, png or webp, up to 15 MB): it is downloaded, resized and stored. The first photo of a group is its cover. Up to 16 per unit and for the venue. It stores existing photos only; it does not create images. 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>",
      "image_url": "<image_url>"
    },
    "name": "add_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out for a photo of the venue as a whole.
image_urlYesDirect link to the photo file.
access_keyYesThe venue’s access key.
make_coverNoTrue puts it first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false); the description adds substantial context on top: the file is downloaded, resized and stored, the first photo of a group becomes the cover, and there are 15 MB and 16-photo limits. It does not address what happens on exceeding the cap or on re-adding the same link, despite idempotentHint=false.

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?

Front-loaded with the core action and target, then constraints, then limits. Five short sentences carry a lot of useful information with little waste; the closing sentence about venue/address/access key is mildly redundant with 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 five-parameter write tool with no output schema, the description covers targeting, input format, size limits, storage behavior, and cover semantics. It stops short of explaining the response (e.g., whether a photo ID or position is returned) or failure modes at the 16-photo cap, which leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, but the description adds real meaning: omitting unit_id targets the venue, image_url must be a direct public https file link with allowed formats and size, and make_cover interacts with the 'first photo is cover' rule. The address/access_key usage is also framed as acting on one venue.

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?

States a specific verb and resource (adds a photo) and precisely scopes the target: a unit, or the venue itself when unit_id is omitted. It also rules out what the tool is not ('does not create images'), so an agent can distinguish it from siblings like remove_photo or set_cover_photo without opening any schema.

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?

Gives clear conditions for use: a direct public https link to an existing jpg/png/webp file up to 15 MB, and a cap of 16 photos per unit or venue. It does not explicitly name alternative tools (e.g., whether set_cover_photo should be preferred over make_cover), so there is no when-not-to-use routing.

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