Skip to main content
Glama
jeebus87

reddirect

by jeebus87

Mark Inbox Read

mark_inbox_read

Mark all unread inbox messages as read. Clear your notification queue with a single action.

Instructions

Mark all unread inbox messages as read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'mark_inbox_read' tool logic. It calls Reddit's /api/read_all_messages endpoint and returns a success response or an error.
    async () => {
      try {
        await client.post("/api/read_all_messages", {});
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify({ success: true, marked_all_read: true }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text" as const,
              text: `Error marking inbox read: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema for the tool. Accepts an empty object (z.object({})) as no parameters are needed.
    title: "Mark Inbox Read",
    description: "Mark all unread inbox messages as read.",
    inputSchema: z.object({}),
  • Registration of the 'mark_inbox_read' tool using server.registerTool() with name, schema, and handler.
    server.registerTool(
      "mark_inbox_read",
      {
        title: "Mark Inbox Read",
        description: "Mark all unread inbox messages as read.",
        inputSchema: z.object({}),
      },
      async () => {
        try {
          await client.post("/api/read_all_messages", {});
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify({ success: true, marked_all_read: true }, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text" as const,
                text: `Error marking inbox read: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • The exported register function that is called from src/index.ts to register all inbox tools (including mark_inbox_read) on the MCP server.
    export function register(server: McpServer, client: RedditClient): void {
  • src/index.ts:32-32 (registration)
    The line in the main entry point that registers all inbox tools by calling registerInboxTools(server, client).
    registerInboxTools(server, client);
Behavior2/5

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

The description implies a state change but does not disclose side effects, reversibility, or permissions needed. With no annotations, the description carries full burden and fails to provide sufficient behavioral context.

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 a single sentence that clearly conveys the tool's purpose with no unnecessary words. It is front-loaded and efficient.

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

Completeness3/5

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

While the tool is simple, the description lacks behavioral details such as whether the action is reversible or idempotent. Given no output schema, more context about the effect would improve completeness.

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?

There are no parameters, and the schema coverage is 100%. The description adds no parameter information, which is acceptable given the no-parameter baseline of 3.

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 clearly states the tool's action: marking all unread inbox messages as read. It uses a specific verb and resource, distinguishing it from sibling tools like get_inbox which retrieves messages.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that it should be used after viewing the inbox or that it replaces manual marking.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jeebus87/reddirect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server