Skip to main content
Glama

YouSpot

by com.youspot

Archive email

archive_gmail_message

Archive one Gmail message — it leaves the inbox but stays in All Mail, fully recoverable. Use only when the user asked for the archive; confirm first if it's your own suggestion. Only works on mailboxes connected under a legacy modify grant — current connections are read-only and cannot change the mailbox; the tool says so if not.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoEmail address of the connected mailbox holding the message. Omit to try all connected mailboxes.
message_idYesThe Gmail message id to archive.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses meaningful behavioral details beyond the readOnlyHint annotation: the message remains recoverable in All Mail, and current connections are generally read-only and cannot modify the mailbox. This gives the agent an accurate model of side effects and limitations without needing to test the tool.

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?

The description is compact and every sentence adds distinct value: one explains the effect, one gives the usage rule, and one states the connectivity constraint. It is front-loaded with the most important behavioral fact and wastes no words.

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?

For a simple two-parameter mutation with no output schema, the description covers what the tool does, its side effects, when to use it, and its permission limitations. No critical information an agent would need before calling the tool 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?

The input schema already documents both parameters with 100% coverage, including the option to omit 'account' to try all connected mailboxes. The description adds no new parameter-level detail, so the baseline score of 3 applies.

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?

The description states a specific action, 'Archive one Gmail message', and clearly distinguishes the result from other operations by explaining it leaves the inbox but stays in All Mail. This makes the tool's purpose immediately distinguishable from related siblings like search_gmail_messages or create_gmail_draft.

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

Usage Guidelines5/5

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

The description gives explicit guidance on when to use the tool: 'Use only when the user asked for the archive; confirm first if it's your own suggestion.' It also states an important constraint about legacy modify grants versus read-only connections, which helps the agent decide whether the tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YouSpot toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools are scoped to a distinct resource and action, and descriptions do a good job separating close pairs like search_connections vs ask_about_connections or get_my_linkedin_posts vs linkedin_analytics. However, the multiple deletion tools (delete_graph_object, delete_graph_objects, purge_graph_object) and the several file-reading tools are easy to confuse without reading the descriptions carefully.

Naming Consistency4/5

The vast majority of tools follow a clear verb_noun pattern such as create_, get_, list_, search_, send_, and delete_. A handful of noun-phrase outliers like linkedin_analytics, mutual_connections, top_message_correspondents, and what_needs_attention break the pattern, so it is highly consistent but not perfect.

Tool Count1/5

64 tools is an extreme count, far beyond the typical well-scoped 3-15 tool range and even beyond the 25+ threshold for 'too many'. While the server covers many integrations, this many tools creates a heavy navigation burden and would be better split into focused servers per domain.

Completeness3/5

Core graph/CRM operations and read-side integration coverage are strong, with search, get, list, and create tools across most domains. However, there are notable dead ends: no delete_calendar_event, no tracker management beyond create_tracker, and set_follow_up explicitly lacks a read-back query tool, so some natural user requests cannot be completed through the toolset.

Resources