Skip to main content
Glama

Request a photo upload to Google

request_upload_photo
Destructive

Ask the user to approve adding one photo to the Google profile from a public https image address (JPEG or PNG, 10KB to 5MB). On approval GBPly downloads it into the media library and sends it to Google within a few minutes. LOGO and COVER replace the current logo or cover photo. Counts as a publish action for Always allow. No credits.

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>",
      "image_url": "<image_url>"
    },
    "name": "request_upload_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
previewNotrue = dry run: nothing is created, run, charged or sent to Google. Returns what would change, the credit cost and whether it would run straight away under Always allow. Use when the user wants to check first.
categoryNoDefault ADDITIONAL.
image_urlYesPublic https address of the image.
profile_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, openWorldHint, non-idempotent), the description discloses the human-approval gate, the async delivery window ('within a few minutes'), that LOGO and COVER overwrite the existing image, that it counts as a publish action under Always allow, and that it costs no credits. This is exactly the extra context the annotations cannot convey.

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 purpose and constraints, then behavior, then cost. Dense and mostly waste-free, though the terse fragment 'No credits.' and the 'Always allow' phrasing rely on product-specific vocabulary that could slow a first-time reader.

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 five-parameter, non-idempotent mutation with no output schema, the description covers cost, timing, replacement effects and approval. It stops short of saying what happens to a pending or rejected request or how to verify the outcome, which an agent would likely need.

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 60%, and the description fills key gaps: the image_url constraints (public https, JPEG/PNG, 10KB-5MB) and the special meaning of the LOGO/COVER categories as replacements. It says nothing about the description or profile_id parameters, but those are comparatively self-explanatory.

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?

The description names a specific verb and resource (upload one photo to the Google profile), plus the source constraint (public https address, JPEG or PNG, 10KB-5MB). It is clearly distinguishable from siblings like request_create_post or request_profile_update, which touch different resources.

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 approval workflow ('Ask the user to approve') and the LOGO/COVER replacement semantics imply when the tool applies, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. where to go for non-photo profile changes or how to follow up on an approved upload). Usage is inferable rather than 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