Skip to main content
Glama

Refine Job Search

by co.getrefine
OverviewDiscussionsAdmin

inbox.refresh

Check Gmail for new mail now; returns per-account sync status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / properties / data / items / additionalProperties
      Previous value: -{}New value: +false
    • removedOutput schema / properties / data / items / properties / calendar_granted
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Whether Calendar read access is granted"
-}
    • removedOutput schema / properties / data / items / properties / calendar_write_granted
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Whether Calendar write access is granted"
-}
    • removedOutput schema / properties / data / items / properties / gmail_granted
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Whether Gmail read access is granted"
-}
    • removedOutput schema / properties / data / items / properties / gmail_send_granted
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "boolean"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "Whether Gmail send access is granted"
-}
    • addedOutput schema / properties / data / items / properties / mailbox / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "number"
+          }
+        ],
+        "description": "Stable resource identifier"
+      },
+      "last_synced_at": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "When the mailbox last finished synchronizing"
+      },
+      "state": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Mailbox synchronization state"
+      },
+      "syncing": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "kind": {
+                "anyOf": [
+                  {
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "messages_processed": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "messages_seen": {
+                "anyOf": [
+                  {
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Current mailbox synchronization progress"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent action. The description adds that it returns per-account sync status, which is useful context, but it does not disclose any side effects, prerequisites, or rate limits. Since annotations cover the safety profile, the added value is modest.

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, focused sentence that front-loads the action and includes the return value. It is concise with no unnecessary information.

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 tool with no parameters and an output schema, the description provides the essential information: what it does and what it returns. It does not mention potential rate limits or authentication, but these are likely inherent to the action and not critical for choosing or invoking the tool.

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?

There are no parameters, so the description has nothing to add about parameter semantics. The empty schema fully covers the absence of parameters, meeting the baseline for a 0-parameter tool.

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 action (check Gmail for new mail now) and the resource, and specifies the return (per-account sync status). It distinguishes itself from inbox.sync_status, which likely only reports status without triggering a check.

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?

The word 'now' implies a manual forced refresh, but there is no explicit statement about when to use this tool versus alternatives like inbox.sync_status. No exclusions or alternatives are mentioned, so usage is implied rather than explicit.

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

All Refine Job Search toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources