Skip to main content
Glama

Mark Conversation Unread

mark_conversation_unread
Idempotent

Mark a Canvas Inbox conversation as unread so it reappears for follow-up. This changes only your view and can be reversed by marking it read.

Instructions

Mark one Inbox conversation as unread so it shows up again. Only affects you. Reverse with mark_conversation_read.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "mark_conversation_unread"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesInbox conversation ID (numeric string). Get it from list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Inbox conversation ID (numeric string). Get it from list_conversations."
  2. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so safety is covered. The description adds two real behavioral facts beyond that: the change is scoped to the caller only, and it can be undone with mark_conversation_read. It doesn't say whether the conversation must currently be read or how failures behave.

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?

Three short sentences: effect first, scope second, inverse tool last. Zero filler and no restating of the title.

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?

For a one-parameter state toggle with full annotation coverage and no output schema, the agent has what it needs to call correctly and to undo the call. Only minor gaps remain, such as what happens when the ID is invalid or the conversation is already unread.

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% and the single conversation_id parameter already documents its format and its source (list_conversations). The phrase 'one Inbox conversation' reinforces that the parameter takes a single ID, but adds no syntax or edge-case meaning beyond the schema. Baseline 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?

States a specific verb ('Mark ... as unread') on a specific resource ('one Inbox conversation'), with the effect ('so it shows up again') and the unit scope ('one'). It also names the inverse sibling, mark_conversation_read, so the agent can distinguish the pair without opening either schema.

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

Usage Guidelines4/5

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

Gives clear context: unread state is per-user ('Only affects you') and is reversible via mark_conversation_read. It does not spell out when-not to use it (e.g. versus batch_update_conversations or mark_all variants), which keeps it short of a 5.

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