mcp-template

gmail_mark_thread_done

Mark a Gmail thread as done by applying the MCP/Done label, hiding it from the curated inbox and updating the curation ledger. Use during triage to process the next thread.

Instructions

Mark a Gmail thread as done by applying the MCP/Done label (hides from curated inbox). Also marks the thread dismissed in the curation ledger. During a triage pass, continue on to the next uncurated or stale thread.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	No
`thread_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`label_id`	No
`marked_done`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 19, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations provided; description discloses applying a label and marking in a ledger, but lacks details on other side effects (e.g., inbox visibility, thread state changes).

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?

Two sentences; concise but could merge the second sentence about the curation ledger for better flow.

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?

Missing output schema description and parameter explanations; with no annotations, the description should provide more context for a tool with two parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; description does not explain the meaning or expected format of user_id or thread_id beyond the schema, leaving the agent underinformed.

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?

Clearly states the tool marks a thread as done by applying a specific label and hiding it from the curated inbox. Distinguishes from archive and unmark siblings.

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?

Mentions usage during a triage pass and continuing to the next thread, but does not explicitly state when not to use it or describe alternatives among siblings.

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

Deploy Server