Skip to main content
Glama
owlpost

owlpost

flag_message

Idempotent

Set or clear an email's Flagged status to star or unstar a message; use account, folder, and UID to target the exact message.

Instructions

Flag (star) or unflag a message by setting or clearing its \Flagged flag.

Args: account: Account name from list_accounts. folder: Folder containing the message. uid: Message UID. flagged: True to flag (default), false to remove the flag.

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": {
      "account": "<account>",
      "folder": "<folder>",
      "uid": "<uid>"
    },
    "name": "flag_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderYes
accountYes
flaggedNo

Output Schema

NameRequiredDescriptionDefault
uidYes
folderYes
flaggedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "flagged": {
      +      "title": "Flagged",
      +      "type": "boolean"
      +    },
      +    "folder": {
      +      "title": "Folder",
      +      "type": "string"
      +    },
      +    "uid": {
      +      "title": "Uid",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "uid",
      +    "folder",
      +    "flagged"
      +  ],
      +  "title": "FlagState",
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent and non-destructive behavior, so the safety profile is covered. The description adds useful mechanism detail (the \Flagged IMAP flag and the default-on behavior of the flagged arg) but says nothing about permissions, error cases, or what the response contains.

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 states the action, followed by a compact per-argument block. Every line is informative, though the Args section is a docstring rather than agent-oriented guidance.

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

Completeness4/5

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

With an output schema present and rich annotations, the definition needs mainly to cover parameters and mechanism, which it does. Minor gaps are lack of explicit sibling routing and any error/permission notes.

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

Parameters4/5

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

Schema coverage is 0% and every property is title-only, so the description carries the full burden and does so reasonably: it identifies account as coming from list_accounts, explains folder and uid roles, and clarifies that flagged defaults to true and false clears the flag.

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 pair (flag/unflag) and resource (message) plus the underlying mechanism of setting or clearing the \Flagged flag. It implicitly distinguishes itself from siblings like mark_read or move_email, though it never names them.

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 verb; there is no explicit statement of when to choose flag_message over mark_read or other message-mutating siblings, and no prerequisites or exclusions are given.

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