Skip to main content
Glama

Website: copy the client's photos

website_photos_copy

Copy up to 20 photos from https addresses (the client's current site, their Business Profile) into storage with the new website, and get the addresses to use in website_save. Do this for every photo on the old site before launch: they disappear when the domain switches over.

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_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesThe https addresses of the photos
clientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the safety bar is lower. The description adds genuinely useful context beyond them: the 20-photo cap, the https-only constraint, and the launch-time urgency. It does not say what happens when a URL is unreachable or partially fails, which matters for an open-world fetch.

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, zero filler, with the action and the deadline front-loaded. The parenthetical examples of address sources are compact and useful rather than redundant.

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?

With no output schema, the description usefully explains that the tool returns addresses for use in website_save, covering the return value. Combined with the cap and source constraints, an agent has enough to call it correctly; only error/partial-failure behavior is unaddressed.

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 50%: urls is documented in the schema, client is not. The description clarifies that urls are https addresses drawn from the client's current site or Business Profile, which adds meaning beyond the schema. It says nothing about the client parameter, so it only partially compensates 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?

States a specific verb and resource (copy photos), the scope (up to 20, https addresses), the destination (storage with the new website), and the downstream consumer (website_save). An agent can distinguish this from website_photos and website_photos_remove 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 timing guidance: do this for every photo on the old site before launch, with the reason (photos disappear when the domain switches). It also names website_save as the follow-up step. It stops short of explicitly contrasting with website_photos or website_photos_remove, so it is strong context rather than full when/when-not 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.