Skip to main content
Glama

Use a selected Google Drive image as a reference

playground_drive_image_import
Idempotent

Copy one explicitly selected PNG/JPEG/WebP image (up to 8 MB) from your connected Google Drive account into Berrys reference storage, where generation providers can fetch it. Returns a File nodeId: pass it in referenceNodeIds to use it. Requires a connected Drive account belonging to this Berrys user; another agent’s Drive connection is not inherited. Free; no generation starts. Never accepts credentials or a sharing-page URL.

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": {
      "projectId": "<projectId>",
      "accountId": "<accountId>",
      "fileId": "<fileId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_drive_image_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesGoogle Drive file ID to import from the selected connected account.
accountIdYesConnected account ID returned by connected_sources_list.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
nodeIdYes
sha256No
mediaUrlYes
mimeTypeYes
replayedYes
revisionYes
canvasUrlYes
sourceUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the auth-scoping rule that another agent's Drive connection is not inherited, the 8 MB ceiling, the accepted MIME types, that the copy lands in provider-fetchable storage, and that no generation is started. The negative constraint 'never accepts credentials or a sharing-page URL' heads off a common misuse mode.

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 action, then the return-handle, then the prerequisite, then the cost and safety caveats — a sensible ordering for an agent skimming. It is dense but nearly every clause carries an operational fact; the credential/sharing-URL sentence is the one that could arguably be trimmed.

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?

An output schema exists, yet the description still gives the one thing an agent needs downstream — that the returned File nodeId is the reference handle. With auth preconditions, size/format limits, and idempotency covered by schema plus annotations, nothing required to call it correctly is missing.

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 coverage is 100%, so every parameter is already documented in structured form and the baseline applies. The description reinforces the intent of fileId and accountId (an explicitly selected file from the caller's own connected account) but adds no format or syntax detail, and the referenceNodeIds it mentions belongs to a downstream tool rather than this tool's inputs.

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?

Opens with a precise verb+resource+scope: 'Copy one explicitly selected PNG/JPEG/WebP image (up to 8 MB) from your connected Google Drive account into Berrys reference storage'. The source, destination, cardinality, and format limits are all stated, which cleanly separates it from a generic asset import.

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 second sentence tells the agent exactly how to consume the result ('pass it in referenceNodeIds'), and 'Free; no generation starts' clarifies the cost/side-effect model at decision time. It stops short of naming an alternative (e.g., the sibling asset-import path for non-Drive files) or an explicit when-not condition.

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.