Skip to main content
Glama

get_listing_photo

Read-only

Retrieve and inspect a listing photo, including private pending media, to review image details before moderation or publication.

Instructions

Inspect a photo of your user's listing, including private pending media.

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": {
      "id": "<id>",
      "photoId": "<photoId>"
    },
    "name": "get_listing_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
photoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context that private pending media is included, which hints at elevated access scope, but it does not describe authentication requirements, return format, or behavior when the photo is missing.

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?

The definition is a single front-loaded sentence with no wasted wording. It is appropriately brief, though the brevity contributes to the missing usage and parameter detail rather than compensating for it.

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 two-parameter read tool whose annotations already carry the safety profile, the description is minimally adequate. However, with no output schema and zero schema description coverage, it should clarify the two identifiers and at least sketch what inspection returns.

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 neither 'id' nor 'photoId' is documented anywhere. The description implies one identifier refers to a listing and the other to a photo, but it never states that mapping or the UUID format, leaving both required parameters semantically ambiguous.

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 gives a specific verb and resource ('Inspect a photo of your user's listing') and adds scope with 'including private pending media.' It is clear what the tool does, but it never distinguishes itself from the sibling get_listing tool or explains when to inspect a photo versus fetch the listing.

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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative among siblings such as get_listing or list_my_listings. The only usage signal is the implied act of inspecting a photo, which the agent must infer.

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