Skip to main content
Glama

List photos

list_photos
Read-onlyIdempotent

List photos and videos on the Google profile (as last synced), newest first.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "list_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
profile_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds two facts beyond that: results reflect the last sync rather than live state, and ordering is newest-first. It omits pagination behavior and any indication of failure modes (invalid profile_id, empty result).

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?

A single sentence with zero waste, front-loading the verb/resource and appending the two most decision-relevant qualifiers (sync freshness, sort order).

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 simple read-only list tool with no output schema, the description covers what the tool returns at a high level and its freshness guarantee. What is missing is the pagination contract and the meaning of profile_id, both of which are absent from every structured field and force the agent to guess.

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 description coverage is 0%, so the description carries full burden for the three parameters, yet it mentions none of them. limit and offset (pagination) and profile_id (which kind of profile, what happens if it is a non-business profile) are entirely undocumented in both places.

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 and resource ('List photos and videos') scoped to a Google profile, plus the sort order ('newest first'). It doesn't name a sibling like list_posts or list_reviews to disambiguate the many list_* tools, but the resource is distinct enough that an agent can tell them apart.

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?

The phrase 'as last synced' implicitly signals that this tool does not refresh data and that sync_profile is the prerequisite for fresh results, which is a useful inference the agent can act on. However, there is no explicit when-to-use/when-not statement and no named alternative among the numerous sibling list_* tools.

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