Skip to main content
Glama

Read a host's photo library

read_host_photos

Lists up to 50 photos owned by a specified host for quick review from an MCP client; read-only, with uploads and deletion handled on the website.

Instructions

List up to 50 photos belonging to one host you own. This is read-only; uploads and deletion require the website.

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": {
      "host_id": "<host_id>"
    },
    "name": "read_host_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe host's positive integer id (from list_hosts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host_id / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key traits: read-only behavior, a 50-item ceiling, and that write operations are impossible here. It leaves open what happens when a host has more than 50 photos (truncation vs. pagination) and what fields a photo entry contains.

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 short sentences with the scope and cap front-loaded and the read-only caveat immediately after. Nothing is redundant or padded.

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 one-parameter read tool with no annotations or output schema, the description covers scope, cap, and safety profile well. Returned photo fields and over-limit behavior are the only meaningful omissions.

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 100% and the host_id property already documents the positive-integer constraint and the list_hosts provenance. The description only reinforces the ownership condition, adding little beyond the schema, so baseline 3 applies.

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 (list), resource (photos), and scope (one host you own) plus a hard cap of 50, so an agent knows exactly what the call returns. No sibling tool deals with photos, so there is nothing to disambiguate.

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?

'This is read-only; uploads and deletion require the website' explicitly rules out use cases the agent might otherwise attempt, and 'one host you own' signals an ownership prerequisite. It stops short of naming an alternative tool to find a host id, though the schema's reference to list_hosts covers that gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.