Skip to main content
Glama
outscraper

Outscraper MCP

Official
by outscraper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Google Maps Photos

google_maps_photos

Retrieve Google Maps photos for places, including menu, owner, and latest images, using place queries or IDs.

Instructions

Fetch Google Maps photos with the documented /google-maps-photos endpoint.

Best for:

  • place photo extraction

  • menu photo retrieval

  • owner photo and latest photo analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional photo filter tag.
asyncNoDeprecated compatibility flag. Prefer execution_mode.
limitNoMaximum places to process.
queryYesOne or more Google Maps place queries or ids.
fieldsNoSpecific fields to return.
regionNoRegion code.
webhookNoOptional webhook URL for async completion.
languageNoLanguage code.
photos_limitNoMaximum photos per place.
execution_modeNoExecution strategy. Use auto to let the MCP server choose between sync and async.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes
asyncNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.5
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.2.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure, but it only says 'Fetch'. It does not mention async/sync execution modes, webhook behavior, potential rate limits, or any side effects, despite having parameters that imply these behaviors.

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?

Compact, front-loaded, and easy to scan with a short summary and three bullets. No redundant filler, though it could be slightly more informative without losing conciseness.

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?

The schema is rich and an output schema exists, covering parameter and return details. However, with 10 parameters and no annotations, the description could more explicitly explain execution modes, tag semantics, and when to use async, so agents aren't left to infer operational behavior.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the 'Best for' bullets add meaning by mapping use cases to the tag enum (menu, by_owner, latest) and to query-based photo extraction. This goes beyond the bare parameter descriptions in the schema.

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?

Clearly states 'Fetch Google Maps photos' with a specific verb and resource. The 'Best for' bullets (place photo extraction, menu, owner, latest) help differentiate from siblings like google_maps_search and google_maps_reviews, though it doesn't explicitly say what the returned data contains.

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?

Provides clear context via 'Best for', telling an agent when to use it for photo-related needs. It does not name alternatives or exclusions, but the listed use cases are specific enough to guide selection.

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

Deploy Server

Other Tools