Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_unstar

Removes a file or folder from Google Drive Starred by exact name, path, or index, unmarking items no longer needed.

Instructions

Remove a file or folder from Starred.

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": "drive_unstar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact item name in the current location (or in path).
pathNoFolder holding the item ("/A/B" from My Drive, "A/B" relative); default: current.
indexNoIndex from the last drive.list / drive.search.
occurrenceNoWhich item when several share the name (0 = first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say the file itself is untouched (non-destructive), whether unstarring a non-starred item errors, or whether the operation is reversible. The critical 'unstar != delete' distinction is left implicit.

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?

A single front-loaded sentence with no filler. Brevity is appropriate, though it shades into under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool taking four target-identification parameters, no annotations, and no output schema, the description is too thin. It says nothing about how to pick the right item via name vs. index vs. occurrence, or what confirmation the caller gets.

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 name/path/index/occurrence are already fully documented, including defaults and semantics. The description adds no additional guidance on how these interact when identifying the target item.

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+resource: removing an item from Starred. It is clearly the inverse of the sibling drive_star, though it never names that sibling or distinguishes unstaring from trashing/deleting.

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?

Usage is only implied by the name; the description gives no conditions for when to reach for this instead of drive_trash, drive_delete_forever, or drive_star. An agent must infer that this only affects the Starred tag.

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