Skip to main content
Glama

stub

by africa.stub.api
OverviewDiscussionsAdmin

Mark message read

mark_message_read

Mark one message or many as read by the current user. Send id for one message, which returns {error}. Or send ids (up to 1000) to mark many in one transaction, which returns {error, read: [id ...], errors: [{id, message} ...]}. That is partial success: ids this business does not own are skipped and listed in errors, and error is true only when nothing was marked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOne message id to mark read.
idsNoUp to 1000 message ids to mark read in one transaction. Partial success: ids this business does not own are skipped and listed in errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Id of the message."New value: +"One message id to mark read."
    • addedInput schema / properties / ids
      Added value: +{
+  "description": "Up to 1000 message ids to mark read in one transaction. Partial success: ids this business does not own are skipped and listed in errors.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 1000,
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "id"
-]New value: +[]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false. The description goes well beyond that: it discloses that ids not owned by the business are skipped and reported, that `error` is true only when nothing was marked, and that the bulk call is a single transaction. These are exactly the behavioral traits an agent needs.

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 dense sentences, front-loaded with the purpose before branching into the two modes. Every clause carries information about behavior or return shape; nothing is padding.

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?

There is no output schema, so the description carries the return-value burden and does so: it spells out {error} for the single case and {error, read, errors} for the bulk case, plus the partial-success rule. Nothing essential to correct invocation is missing.

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 100%, so the baseline is 3, but the description adds genuine meaning: the mutually-exclusive usage of `id` vs `ids`, the per-mode return shapes, and the 1000-item transactional limit with partial-success semantics.

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+resource ('Mark one message or many as read by the current user') and immediately distinguishes the two operating modes via `id` vs `ids`, so an agent can tell this apart from siblings like mark_message_alerted, snooze_message, or update_message.

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?

Clearly routes the agent between the single-message path (`id`) and the bulk path (`ids`, up to 1000 in one transaction), and explains that partial success is possible. It does not, however, state when to prefer this over sibling message tools or mention any prerequisites.

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

All stub toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources