Skip to main content
Glama
r28ai

recruiting-ops-mcp

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

gdrive_files_create

Creates Google Drive file metadata for folders, Docs, Sheets, Slides, or empty blobs, with one optional parent folder, so recruiting workflows can set up candidate files.

Instructions

Create a file's metadata: a folder (mimeType application/vnd.google-apps.folder), a Google Doc / Sheet / Slide, or an empty blob. Media upload is not expressed here. parents takes at most one folder ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesThe file resource to create. For a folder, set `mimeType` to `application/vnd.google-apps.folder`. For a Google Doc, Sheet or Slide, use the corresponding `application/vnd.google-apps.*` MIME type. `parents` takes at most one folder ID.
ocrLanguageNoA language hint for OCR processing during image import (ISO 639-1 code).
includeLabelsNoA comma-separated list of IDs of labels to include in the `labelInfo` part of the response.
supportsAllDrivesNoWhether the requesting application supports both My Drives and shared drives.
keepRevisionForeverNoWhether to set the `keepForever` field in the new head revision. This is only applicable to files with binary content in Google Drive. Only 200 revisions for the file can be kept forever. If the limit is reached, try deleting pinned revisions.
ignoreDefaultVisibilityNoWhether to ignore the domain's default visibility settings for the created file. Domain administrators can choose to make all uploaded files visible to the domain by default; this parameter bypasses that behavior for the request. Permissions are still inherited from parent folders.
includePermissionsForViewNoSpecifies which additional view's permissions to include in the response. Only `published` is supported.
useContentAsIndexableTextNoWhether to use the uploaded content as indexable text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false (a write) and openWorldHint=true, so the safety profile is partly covered. The description adds a meaningful scope constraint — metadata only, not media upload — but says nothing about permissions, reversibility, or what the response contains.

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, front-loaded sentences with no filler. The core action and the two most consequential constraints (no media upload, single parent) appear immediately.

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?

Given full schema coverage and existing annotations, the description is adequate for calling the tool. However, with no output schema, it omits any statement about what is returned (the created file resource), and gives no hint about required permissions or behavior when the parent is invalid.

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?

Schema description coverage is 100%, so the schema already documents all 8 parameters in detail. The mimeType values and the 'parents takes at most one folder ID' note in the description merely restate what the nested `file` parameter description already provides, adding no new syntax or format information.

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?

States a specific verb and resource ('Create a file's metadata') and enumerates the three things it can create — a folder, a Google Doc/Sheet/Slide, or an empty blob. It does not, however, explicitly distinguish itself from a possible native-doc creator, so the differentiation is only partial.

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?

'Media upload is not expressed here' gives one negative scoping cue (don't use this to upload content), which is useful. But it names no alternative tool and gives no explicit when-to-use conditions, leaving usage largely implied.

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