Refine Job Search

inbox.sync_status

Read-onlyIdempotent

Per-account Gmail synchronization status, including current progress and last sync time

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 22, 2026

removedOutput schema / properties / data / items / properties / email / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / items / properties / email / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / items / properties / id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedOutput schema / properties / data / items / properties / id / type
```
Added value: +[
+  "string",
+  "number"
+]
```

changedOutput schema / properties / data / items / properties / mailbox / anyOf

Previous 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"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "description": "Stable resource identifier",
+        "type": [
+          "string",
+          "number"
+        ]
+      },
+      "last_synced_at": {
+        "description": "When the mailbox last finished synchronizing",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "state": {
+        "description": "Mailbox synchronization state",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "syncing": {
+        "anyOf": [
+          {
+            "additionalProperties": {},
+            "properties": {
+              "kind": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "messages_processed": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "messages_seen": {
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Current mailbox synchronization progress"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / items / properties / primary / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / items / properties / primary / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / data / items / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / data / items / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / meta / properties / next_page / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / meta / properties / next_page / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / meta / properties / total_count / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / meta / properties / total_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```

AddedAug 26, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds per-account Gmail scope and the returned status fields, but does not go beyond that with auth requirements, rate limits, or sync-state caveats.

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?

A single front-loaded sentence with no wasted words. It delivers resource, scope, and returned data immediately.

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?

Given zero parameters, rich annotations, and an output schema, the description is complete enough for an agent to call the tool correctly. It states what the status covers without needing to explain return values or safety behavior.

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?

The tool has zero parameters, so the baseline is 4. The description appropriately avoids describing nonexistent parameters while clarifying that status is per-account.

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 names a specific resource (Gmail synchronization status) and scope (per-account), and identifies the information returned (current progress and last sync time). It is clearly distinguishable from sibling actions like inbox.refresh or integrations.connect_google.

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 implied: an agent can infer this is the read-only status check, but the description does not explicitly state when to use it versus inbox.refresh or other inbox tools. No alternatives or preconditions are mentioned.

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 tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?