Skip to main content
Glama

Website: the client's photos and upload link

website_photos
Read-onlyIdempotent

The photos stored for a client's new website, and the upload link the agency or the client opens to add photos from a phone or computer. Photos are stored with the site so they keep working after launch (photos on the old site disappear when the domain switches over). Use real photos of their work only, never stock.

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>"
    },
    "name": "website_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already cover the safe, read-only, idempotent, and non-destructive profile, and the description adds real context beyond that: photos live with the site so they survive launch, and photos on the old site vanish when the domain switches. The upload link's channel ('from a phone or computer') is also disclosed, which the annotations do not convey. It stops short of stating whether the link is reused, expires, or is shared across clients.

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 sentences, front-loaded with what the tool returns, followed by the persistence rationale and the no-stock rule. Each sentence does work; only the persistence clause is slightly verbose given it partly repeats the storage idea.

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 one-parameter tool with no output schema, the description is largely sufficient for what the tool returns and why. However, the undefined identifier format and the absence of any output-structure or link-lifetime detail leave a real gap an agent will hit at call time.

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

Parameters2/5

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

Schema coverage is 0% for the single 'client' parameter, so the description would need to compensate and it does not. It never says whether 'client' is a name, an ID, a slug, or a domain, which is the main ambiguity an agent must resolve before calling.

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?

The description names a specific resource class: the photos stored for a client's new website plus the upload link used to add more. It is clear what the agent gets back, though it phrases the tool as a noun phrase rather than a verb (list/retrieve), and it does not distinguish itself from the website_photos_copy or website_photos_remove siblings.

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 by 'for a client's new website', so an agent can infer this is the pre-launch photos step. The one explicit directive, 'Use real photos of their work only, never stock', is a content rule rather than a when-to-call-this-vs-alternatives rule, and no sibling is named as an alternative.

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.