Skip to main content
Glama
Sign In
Google Sites MCP

Google Sites MCP

by RXDG2908
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upload a local file to Google Drive

gsites_upload_to_drive

Uploads a local file to My Drive in a separate tab without changing sharing, so the Google Sites editor stays untouched; embed it afterward with gsites_add_drive_file.

Instructions

Upload a local file (video, PDF, zip...) to 'My Drive' through the Drive web UI, in a separate tab so the editor is untouched. It does NOT change sharing. Afterwards embed it with gsites_add_drive_file.

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": {
      "file_path": "<file_path>"
    },
    "name": "gsites_upload_to_drive"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path of the file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world operation; the description adds real context beyond them by saying the upload happens through the Drive web UI in a separate tab and that sharing is not modified. It stops short of covering auth requirements, size limits, or what happens on failure, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the action and destination, then the operational note, then the follow-up call. Nothing is redundant and the sequencing guidance is placed where it is read first.

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 single-parameter tool with full schema coverage, no output schema, and informative annotations, the description covers what it does, how it behaves (separate tab, sharing unchanged), and what to do next. Only minor gaps remain, such as where the uploaded file identifier comes from for the subsequent embed step.

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

Parameters3/5

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

There is only one parameter and the schema fully documents it ('Absolute path of the file', minLength 1), so the schema carries the semantics. The description's file-type examples (video, PDF, zip) hint at what kinds of files are acceptable but add no path format or validation detail beyond the schema; baseline 3 applies at 100% coverage.

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?

States a specific verb and resource ('Upload a local file ... to My Drive') and gives concrete examples of accepted content (video, PDF, zip). It also distinguishes itself from the sibling that consumes the result, gsites_add_drive_file, so an agent can tell the two apart without opening schemas.

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?

The description makes the workflow position explicit: upload first, then 'embed it with gsites_add_drive_file', which names the alternative/complementary tool and the ordering. It does not spell out a when-not-to-use case, but the 'separate tab so the editor is untouched' note clarifies the operational context well.

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