Skip to main content
Glama
Sign In
findme-mcp

findme-mcp

Official
by findmephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

upload_photos_from_drive_folder

Redirects to the FindMe web app to import photos from a Google Drive folder using Google Picker for authorization.

Instructions

Attempt to import photos from a Google Drive folder. IMPORTANT: this is not supported in chat-based AI assistants because Google's drive.file scope (the only Drive scope FindMe is verified for) does not allow apps to list folder contents. The tool always returns a redirect message pointing the photographer at the FindMe web app, where the Google Picker handles authorization in one click. Surface the message verbatim — do not retry or guess folder contents.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_photos_from_drive_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idNo
folder_idNoGoogle Drive folder ID (optional, ignored).
folder_urlNoGoogle Drive folder URL (optional, ignored).
folder_nameNoOptional folder name for display.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool always returns a redirect message instead of actual photos, explains the Drive scope limitation, and instructs the agent on proper handling. This is highly transparent.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the purpose, then warnings, then actionable instruction. Every sentence is essential, with no wasted words.

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?

Given the tool's complexity (unsupported in chat, Drive scope limitation) and lack of output schema, the description covers all needed information: what it does, why it fails, how to handle the result. Parameter behavior is contextualized appropriately.

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 75%, and the description adds value by implying that folder_id and folder_url are ignored (since the tool always returns a redirect). It also clarifies that folder_name is for display. While not explicit for all parameters, it provides meaningful context beyond 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?

The description clearly states the tool attempts to import photos from a Google Drive folder, using a specific verb and resource. It distinguishes from sibling tools like upload_photos_from_paths and upload_photos_from_urls by focusing solely on Drive folders.

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?

The description explicitly states the tool is not supported in chat-based AI assistants due to Drive scope limitations, and instructs the agent to surface the redirect message verbatim and not to retry or guess. This provides clear when-to-use and when-not-to-use guidance.

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