Skip to main content
Glama

posterly

by ly.poster
OverviewDiscussionsAdmin

manage_google_business_media

Destructive

Change a Google Business Profile gallery (the photos and videos shown on Maps and Search). action=add (source_url, category): add a photo or video from a public https URL (upload it with upload_media first); COVER and PROFILE are single-slot and replace the existing one. action=delete (media_name from list_google_business_media): permanently remove an item from the public profile. Both use preview then confirm: call without confirm to get a preview and preview_id, show it, then call again with confirm=true and that preview_id.

Input Schema

NameRequiredDescriptionDefault
actionYesadd or delete.
confirmNoLeave out to get a preview. Set true only after the user explicitly approved it, with the preview_id.
categoryNoadd: which gallery category to add the media to.
account_idNoGoogle Business social account ID from list_accounts.
media_nameNodelete: full media resource name from list_google_business_media (accounts/.../locations/.../media/...).
preview_idNoThe preview_id from the preview call. Required with confirm: true for actions that preview first.
source_urlNoadd: public https URL of the photo or video (from upload_media). Photos must be JPG or PNG, 10 KB to 5 MB.
location_idNoGoogle Business numeric location id (the location_id/platform_user_id from list_accounts, e.g. "197940849675145390"). NOT the ChIJ... Place ID from list_google_business_reviews view=review_link. Prefer account_id.
media_formatNoadd: defaults to PHOTO. Use VIDEO for videos (Google caps profile videos at 30s / 75MB).
workspace_idNoFilter to a workspace ID from whoami.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Leave out to get a preview and preview_id. Set true only after the user explicitly approved the preview, together with preview_id."New value: +"Leave out to get a preview. Set true only after the user explicitly approved it, with the preview_id."
  2. Changed1 schema field changed
    • changedInput schema / properties / source_url / description
      Previous value: -"add: public https URL of the photo or video (from upload_media)."New value: +"add: public https URL of the photo or video (from upload_media). Photos must be JPG or PNG, 10 KB to 5 MB."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotency, and the description adds value beyond them: delete is 'permanently remove' from the public profile, COVER/PROFILE are single-slot (implicitly overwriting the existing image), and the preview/confirm gate must be shown to the user before committing. That is exactly the destructive/mutation context an agent needs.

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?

Front-loaded with the resource then action=add / action=delete / shared-flow segments, and every sentence carries actionable content. It is dense and slightly packed, but there is no filler to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter destructive mutation with no output schema, the description covers prerequisites, per-action requirements, overwrite semantics, and the confirm workflow. An agent has everything needed to call it correctly without further discovery.

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; the description nonetheless adds decision-relevant meaning by binding parameters to actions (source_url/category for add, media_name for delete) and clarifying the COVER/PROFILE single-slot behavior and preview_id reuse. It stops short of explaining every field, but meaningfully exceeds the schema.

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?

Names a specific resource (Google Business Profile gallery of photos/videos on Maps and Search) and two explicit operations (add, delete). It also points at the relevant siblings (upload_media, list_google_business_media), so an agent can distinguish it from list_google_business_media or upload_media without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use routing per action (add requires source_url+category sourced from upload_media; delete requires media_name from list_google_business_media), plus the mandatory two-step preview-then-confirm flow with the exact condition to set confirm=true. Nothing is left to inference.

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

All posterly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources