Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_unstar

Remove stars from Gmail conversations selected by search, folder, row index, or subject match to clear starred status in bulk.

Instructions

Remove the star from conversations.

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

Input Schema

NameRequiredDescriptionDefault
allNoAct on EVERY conversation of the query/folder list (Gmail's 'Select all' after loading the whole list; repeated until the list is empty for actions that remove conversations from it). Needs query or folder; no index/indexes/match.
indexNoRow index from gmail.list / gmail.search (0 = first row).
matchNoSelect every row whose subject contains this text (case-insensitive).
queryNoRun this Gmail search first and take the rows from its results.
folderNoOpen this folder/label first and take the rows from it.
indexesNoSeveral row indexes (multi-selection).
max_rowsNoWith match, look at most at this many rows from the top.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

There are no annotations, so the description carries the full disclosure burden and provides almost none: it doesn't say the change is reversible, whether it operates on one or many conversations, or whether a prior gmail.list/gmail.search is required to supply indexes. Only the bare implication of a star-removing mutation comes through.

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 zero filler. It is efficient, though its brevity is arguably under-specification rather than disciplined concision, which is penalized in other dimensions.

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

Completeness1/5

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

A tool with seven optional parameters, no required inputs, no annotations, and no output schema gets one sentence with no explanation of selection modes or prerequisites. An agent cannot determine from the description how to target the right conversations.

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 each of the seven selection parameters (all, index, indexes, match, query, folder, max_rows) is already well documented in the schema. The description adds nothing beyond the plural 'conversations', so baseline 3 applies.

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 ('remove the star') and resource ('conversations'), which cleanly mirrors the sibling gmail_star. It does not explicitly name gmail_star as the inverse, but the operation is unambiguous from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no mention of alternatives such as gmail_star or gmail_important. Critically, it never explains that a conversation must be selected via index/indexes/match/query/folder/all, which is the central decision the agent must make before invoking.

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