Skip to main content
Glama

List Job Photos Tool

list-job-photos
Read-only

Lists authorized private photos attached to one job with protected download URLs, filenames, captions, and media types. Use to list job photos in the connected business. Returns job_id, count, photos, scope.

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": {
      "job_id": "<job_id>"
    },
    "name": "list-job-photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob ID returned by search-jobs.

Output Schema

NameRequiredDescriptionDefault
countYesCount for the returned result.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
job_idYesJob id for the returned result.
photosYesBounded photos records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / required
      Added value: +[
      +  "job_id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Count for the returned result.",
      +      "type": "integer"
      +    },
      +    "job_id": {
      +      "description": "Job id for the returned result.",
      +      "type": "integer"
      +    },
      +    "photos": {
      +      "description": "Bounded photos records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "job_id",
      +    "count",
      +    "photos",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, closed-world operation, so the bar is lower. The description still adds real context beyond them: the photos are 'authorized' and 'private,' and the returned download URLs are 'protected,' which signals an authorization requirement and non-public asset handling not visible in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core action and returned fields, but the second sentence ('Use to list job photos in the connected business') is redundant with the first and does not earn its place. The final sentence duplicates the output schema's field list.

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 single-parameter read tool with an output schema and annotations, the description covers scope, authorization nuance, and return shape adequately. The only real gap is usage routing versus other job-scoped tools.

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 single job_id parameter is already documented with its source (search-jobs). The description adds no further meaning about the parameter, so the baseline 3 applies.

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 verb and resource ('Lists authorized private photos attached to one job') and scopes it to a single job, so an agent can tell it apart from general job tools like get-job. It stops short of naming a sibling alternative, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is 'Use to list job photos in the connected business,' which restates the tool name rather than saying when to choose it over get-job or other job-scoped tools. No prerequisites (e.g., that job_id must come from search-jobs) or exclusions are stated.

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